How to configure Connection Alias with multiple endpoints and credentials based on runtime

DScroggins · ‎04-01-2019

Hello,

Im trying to configure a Connection & Credential Alias for use within a Flow IntegrationHub REST Step. What I would like to do is to configure the Connection Alias with both a Development/ Test Endpoint & Credentials, as well as, the Production Endpoint & Credentials so that at runtime the Flow can determine which instance the flow is running in and then determine the proper endpoint & credentials to use. I have only previously configured an Alias with a single active connection but know that the latter is possible. I've read through the docs and am still stuck on how to properly configure the Alias. Any assistance would be most appreciated.

Thank you for your time.

--David

DScroggins · ‎04-05-2019

I figured out a solution that works for us so will post it here just in case anyone else is looking to do the same thing.

If you have an integration with a system that uses different endpoints and/or credentials for different environments i.e .Dev, Test, Prod then you can configure a connection alias during your development work of the integration (In our case this was in an IntegrationHub REST Step). During the development of the Integration we simply linked up the Connection Alias and then in each respective instance we configured and associated an appropriate connection record with the endpoint & credentials needed for each instance. The connections and credentials are preserved during clone downs so they are not overwritten in the sub-prod instances . When the Integration step is called during runtime in each instance it simply references the configured connection alias and will utilize the connection/credentials that are defined in the instance at that time.

Hopefully this will help someone else who finds themselves with a similar need.

View solution in original post

surya123 · ‎04-20-2020

Is there a way we can extract the value of connection name from the integration metadata?

Luis Franco · ‎04-28-2020

Hi, David.

I've implemented the same logic but using the sn_cc.ConnectionInfoProvider() API to get the atributes information.

The problem is that on run time the users without read access to the connection table are being denied access to the information, even if this is running on server script include.

Did you have this problem too?

Thank you.

Best,

Luis Franco

DScroggins · ‎04-29-2020

Hi Luis,

No we do not have it set up in that manner so have not run into that issue. I have however tried to implement it in my dev instance and can confirm I get the same security constraints error when calling sn_cc.ConnectionInfoProvider() API from a Script Include using normal user account. I think that is odd behavior as Script Includes are supposed to execute as system in my understanding. But it is being blocked by this ACL:

https://{INSTANCE}.service-now.com/sys_security_acl.do?sys_id=c451f70db3323200350086d256a8dcf3

How/Where are you attempting to initiate this bit of code? BR? Flow? Workflow? If it is from a Flow or WF then you can force the API to be called from the System instead of the user.

--David

Luis Franco · ‎04-30-2020

Hi, David.

I'm using a GlideAjax call from the service portal to the script include in a scoped app.

I tried the gs.getSession().impersonate() but it's not available in scoped applications.

I managed to implement this by using GlideRecord but it was quite challenging because of the connection attributes.

I'm adding this solution in my initial community post on the issue here.

Thank you for your input.

Best regards,

Luis Franco

panda1 · ‎09-21-2022

hi,@Luis Franco

I also encountered this problem. How did you solve it