adamb.16374 (Praxedo) asked a question.
How to redirect on different servers based on user attribute with OIDC
Hi,
We have an application that is hosted on different servers, reachable through different URL ( node1.company.com, company.app.com ...)
Currently (before Okta integration), we have an app to centralize the login (login.company.com). Based on its database, it redirects users to the node it has been created on.
We would like to have something equivalent with okta. We have added an attribute to the users of the app (NODE) that can be node1, node2 etc...
What solution would we have to get Okta to redirect on a dynamic URL based on that attribute ? Our ideal solution would be to have Okta host a login page for us and do that, but we are opened to anything.
Cordialement,
Adam
To clarify, I meant (node1.company.com, node2.company.com...)
Hi, @adamb.16374 (Praxedo)
Thank you for posting on our Community page!
I am not sure I understand the use case, but I found an article that might help:
https://help.okta.com/en-us/Content/Topics/Security/configure-routing-rules.htm
Thank you for reaching out to our Community and have a great day!
_____________________________________________________________________________
Watch and Learn: New Okta how-to videos, plus what's new this month in the May newsletter.
_____________________________________________________________________________
Community members help others by clicking Like or Select as Best on responses. Try it today.
_____________________________________________________________________________
Routing rules will get you there, but also consider non-Okta infrastructure. A proxy sitting in front of your applications that accepts the OIDC id_token from Okta, handles the validation/verification and then forwards the client onto the correct node is probably the better answer here. Almost any API gateway should handle that for you.