go to post Marykutty George · Apr 5 We have the same task set up and it is scheduled on demand but I tested it for 1hr, 5min and 10mins and it is working okay. It could be something specific on your config. Is there anything useful in the Task history results?
go to post Marykutty George · Feb 7 This issue is resolved now. Problem was missing Unauthenucated access configuration. /isc/pki weba pplication should have unauthenticated access enabled to get the certificate information to diaply in the tab above.
go to post Marykutty George · Feb 1 May be you could try simply passing message to the required namespace: Create two operations in the current namespace Configure one of the operation as TCP connection to a business service in the second namespace where you have the required operation(see sample config) Configure the business service in the second namespace as pass-through to the required operation in that namespace
go to post Marykutty George · Dec 28, 2022 Login to WRC and use the online distribution link https://wrc.intersystems.com/wrc/coDistGen.csp
go to post Marykutty George · Oct 3, 2022 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
go to post Marykutty George · Sep 29, 2022 @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.
go to post Marykutty George · Sep 29, 2022 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
go to post Marykutty George · Sep 15, 2022 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.
go to post Marykutty George · Aug 25, 2022 If you are trying to alter a persistent class you may need to check if the DDL statements are allowed for the class (DdlAllowed keyword) https://docs.intersystems.com/healthconnect20211/csp/docbook/Doc.View.cl...
