Question
Optum
US
Last activity: 19 Mar 2019 11:12 EDT
ASO doesn't work if same credentials used by multiple applications
We have quite a few automations that span multiple different applications. Some of these applications use the same log in credentials, but do not use single sign on so they need to be signed in to individually. We have the credentials set up using ASO.
If we only have one application launch then it is able to successfully pull the credentials and sign in to the applications. As soon as we add a second application that needs to access the same set of ASO credentials neither one of them grabs the credentials.
I'll note that one of the automations uses the out of the box option to do the sign in, where it enters the credentials as soon as the page is created. Whereas the other automation programmatically grabs the credentials from the ASO store and enters it into the username and password text boxes.
We have searched for an answer to this, but have found none so far.
so if anyone knows why we aren't able to use the same set of ASO credentials for multiple applications please help!
If you need any other information please ask and I'll do my best to provide.
Accepted Solution
Optum
US
That is what we had, but it still didn't work. We eventually got it to work, using the group field in the credentials manager that's attached to the adapter.
Took awhile to figure out since there aren't any examples of how to do it in the documentation for the credentials manager. It may be useful for others if one was provided instead of just a brief description.
Solution:
In each adapter that needs to use the same set of credentials, you can assign the same group name (e.x. Group = "TestGroup") for each one, then set the application key to the something else, we used the app name (e.x ApplicationKey = "App1"). Once you build and run it, you can click on set Credentials and you will see the name column as your group name and there will be a new column called applications that will contain the ApplicationKey names you set for each credential in the group.
Accepted Solution
Optum
US
That is what we had, but it still didn't work. We eventually got it to work, using the group field in the credentials manager that's attached to the adapter.
Took awhile to figure out since there aren't any examples of how to do it in the documentation for the credentials manager. It may be useful for others if one was provided instead of just a brief description.
Solution:
In each adapter that needs to use the same set of credentials, you can assign the same group name (e.x. Group = "TestGroup") for each one, then set the application key to the something else, we used the app name (e.x ApplicationKey = "App1"). Once you build and run it, you can click on set Credentials and you will see the name column as your group name and there will be a new column called applications that will contain the ApplicationKey names you set for each credential in the group.