-
I create my node openid client "client" with an internal provider URL, "provider". I then attempt to auth in my front-end app to my provider through a redirect link that the client provides. When my app is redirected to the my provider, the internal url is returned and the app cannot resolve it. How can I design around this? So, my app GETs a /login route from my client For context, I am running my client in kube, with my oidc provider. My client would not be able to resolve the internet Url for my provider that my app is expecting. So, I need to config it with private, but return a public. Any ideas? @panva Any help, is much appreciated. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@corinz configure your Issuer instance authorization_endpoint to be the "internet" one. You will probably not be able to use discovery but you can still construct the Issuer manually with just the metadata. |
Beta Was this translation helpful? Give feedback.
@corinz configure your Issuer instance authorization_endpoint to be the "internet" one. You will probably not be able to use discovery but you can still construct the Issuer manually with just the metadata.