Yes... 

I have no issues with VSCode, its just the one user. The issue with the user I believe is with LDAP not InterSystems as the same error happens when trying to sign into the Management Portal, periodically. 

Does /api/atelier need to have unauthenticated turned on? Why am I seeing the 

ERROR #815: User not authorized for service %Service_WebGateway
Web Application: /api/atelier

I don't want Unauthenticated users to access the system or be able to get through the Web Gateway at all...

Yes I am attempting to connect to Epic Interconnect using OAuth 2.0. I created an internal backend application on vendor services and supplied it with a public key I had generated from our IRIS server. 
 

I just haven’t found the right sequence of code or syntax for the request to happen yet. I’m working with WRC but since Epic suggested using JWT and our systems team doesn’t have a jwks setup it’s been kind of a hard thing to figure out. 

I was able to get past the ERROR #5659: Property 'OAuth2.AccessToken::SessionId(6@OAuth2.AccessToken,ID=)' required by specifying an ID at the end of the request...

%SYS>set url = ##class(%SYS.OAuth2.Authorization).GetAuthorizationCodeEndpoint("EpicFHIRPOC",scope,OAUTHURL,.properties,.isAuthorized,.sc,,123)

so the sc returns 1, however isAuthorized is still returning 0. If I run IsAuthorized, I am not seeing any errors.

Am I taking the correct steps? How do I get the Token?

How did you configure the web gateway to do this?

Each web gateway is configured to talk to the local Health Connect instance, irrespective of it being primary, secondary or DR at any time.

So, when have to access the primary, we go via the VIP URL -> the request lands on the IIS for the primary instance and that is passed on to the local Health Connect instance.

It is something with the password that is setup during the Install process vs the password that is on the user. I installed IRIS with setting the password as a default, verified that I could get into the Web Gateway Management, but as soon as I changed the password through the Security within the Management portal, I could no longer get into the Web Gateway Management.

So do I have to modify the CSP.ini somehow to tell it to use the LOCAL password, vs the SYSTEM password?

While thinking about this, I am wondering if using an encryption key might be a possible solution as well that way there is limited access to the password, and the key would just have to be regulated to be updated every so often. With using a AD service account, the password still needs to be updated or kept up to date, and still needs to be passed into the shell script for Terminal to open.

I have submitted the following IDEA...

https://ideas.intersystems.com/ideas/DPI-I-466