Recent posts:
show all 3
Recent replies:
show all 8
Neil Thaiss · Feb 22, 2021

Hi Pravin,

Thank you for your very detailed answer.

However, on investigation, I found that I didn't need any of this, as all the client and server configurations are stored in the HSSYS database, as are the access tokens, when they are created.

The %SYS namespace then contains a global mapping for OAuth2.* from the HSSYS database.

So, by mirroring the HSSYS database and setting the 'Customization namespace' to HSSYS in the OAuth2 server configuration, allows OAuth2 to continue to work after a failover.

Neil

Neil Thaiss · Feb 17, 2021

Hi McLean,

Thank you for your reply, very useful.

With regards to failover and the necessary OAuth2 components this was my biggest concern as I had assumed these components where store in the %SYS database, which isn't mirrored.

However, you saying that they are stored in the HealthShare database made me think and I can now see that they there is a global mapping for the HSSYS database, which can, I'm sure, be mirrored.

I have gone through a lot of documentation, but is there any particular links, that relate to this specific area that you could pass on?

Thanks again.

Neil

Neil Thaiss · Feb 8, 2021

Also try putting brackets around the top number of rows, Jerry,  i.e.: TOP (100).

I've known this to be a problem for me with linked tables.

Followers:
Neil has no followers yet.
Following:
Neil has not followed anybody yet.
Global Masters badges:
Neil has no Global Masters badges yet.