Thank you so much for your help @Jorge de la Garza.

I configured the endpoint manually and configured the client details but not getting the access token back. I have created a WRC ticket to get some help from the support team. 

Thank you for help with this issue. 

Mary 

@Jorge de la Garza  Thank  you so much for your help with this issue. 

I think what I need to achieve is to get the HealthShare discovery functionality to use the specific URL for the auth server instead of the openID connect call with .well-known/openid.configuration , mainly because  it will be the Integration engine which uses the access token to get the resources and transform it to HL7 or other format of message and send it to other systems. 

Discovery URL for the authorization server I need to connect is https://xxxxx.cerner.com/r4/xxxxxxxxxxx/metadata but if by default the HealthShare OAuth discovery option is using the OpenID format (.well-known/openid.configuration) , this URL becomes invalid. Is there any way to specify the OAuth2.0 Client Discovery option to not use the openID connect and just use the URL provided in the Issuer endpoint ? 

Apologies if I am asking silly question here . I am new to OAuth.

Thank you @Jorge de la Garza .

I tried the URL with /.well-known/openid-configuration and it failed. I manged to get the correct OpenID discovery url from the  Cerner documentation and I can see the return parameter when I use the new URL in the browser but it not working in the HealthShare OAuth configuration. I am getting Unexpected issuer claim  error 

I enabled the ISCLog to 10 but it is not showing any useful information about the error. 

Also can I please check, if the OAUth configuration in HealthShare can any option other than OpenID connect for discovery?

Thanks

Thank you  @Cristiano Silva 

Thanks @Cristiano Silva  

Is there any way to get more information on this alert from the system ? I can see these alerts in message log but it is not very clear from the alert which client connection was disconnected or anything else. 

Thank you @Jeffrey Drumm 

Thank you @Justin Owens  and @Alex Woodhead .  I managed to combine both your ideas and managed to create a custom task to get the system dashboard information written to a file every hour without the file getting overwritten. 

Thanks @Jeffrey Drumm 

Setting the config for each namespace worked. 

Thank you Sergey. I will check this. 

Hi Jeffrey, 

I did try both option below but both had no impact on the behavior. 

set ^%SYS("Portal","EnableAutoRefresh")=0

and

set ^%SYS("Portal","EnableAutoRefresh")=1

Intersystem Documentation for this is a bit confusing for this one but what I understand is : setting EnableAutoRefresh =1 actually make automatic refreshes off by default.

set ^%SYS("Portal","EnableAutoRefresh") = 1

If you do so, a set of radio buttons appears on Management Portal pages that can be refreshed, enabling users to turn automatic refreshes on and off. On some pages, users can specify the refresh interval. Importantly, when you set the EnableAutoRefresh node to 1, automatic refreshes are off by default.  

https://docs.intersystems.com/healthconnectlatest/csp/docbook/Doc.View.c... 

Thank you @Vitaly Furman  for explaining it.  

We are only handling one message type (ORU_R01) and the data items are fixed so I think it I will go with the first approach. 

Thank you @Vitaly Furman. 

Thank you Shackcham.

Thank you @Jordan Simpson . This was helpful to solve my issue. 

Thank you @Evgeny Shvarov. I was looking for an individual table/global level size check.