MicahR.28129 (Customer) asked a question.
Background: We have an existing SSO integration set up with one of our vendors that uses an inline hook to populate a few SAML assertions. The inline hook accepts the Customer ID on the customer's profile and our API adds the necessary attributes to the SAML assertion. This is all configured in our customer Okta tenant.
We are setting up another integration within our internal workforce Okta tenant for our employees that connects to the same application, and we need our employees to be able to login on behalf of (impersonate) the customer. Our problem is that we're not sure how to get the customer ID the employee is working with to Okta so that it can be consumed by the same inline hook. Is there a way to send a custom value within an Okta app authentication attempt that can then be passed to our inline hook? Perhaps in the app embed link? We have ways of obtaining the current customer ID our employee is working with, we are just trying to determine where to send it.
Hi @MicahR.28129 (Customer) , Thank you for reaching out to the Okta Community!
I know of no out-of-the-box solution for this but perhaps you can check with our colleagues on the dedicated Developer Forum devforum.okta.com to take advantage of their expertise.
You can also consider submitting this as a Feature Request on the Okta Community page by going to the Community→ Ideas tab. Features suggested in our community are reviewed and can be voted and commented on by other members. High popularity will increase the likelihood of it being picked up by the Product Team and it being implemented.
More details here:
https://support.okta.com/help/s/blog/a674z000001cj7YAAQ/okta-ideas-faq?language=en_US
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.