Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/DatabaseStatus wrong redirect_uri when using Keycloak? #898

Open
StefanSchuhart opened this issue May 4, 2022 · 1 comment
Open

/DatabaseStatus wrong redirect_uri when using Keycloak? #898

StefanSchuhart opened this issue May 4, 2022 · 1 comment

Comments

@StefanSchuhart
Copy link

Hi,

using Keycloak as auth-provider, it seems that the redirect_uri parameter for the redirection from Keycloak-Login page back to https://{myDomain}/DatabaseStatus is incorrect.

When clicking on DatabaseStatus the Login-URL (auth/realms/frostrealm/protocol/openid-connect/auth?response_type=code&client_id={myClientID}&redirect_uri=http%3A%2F%2F{myDomain}%2FFROST-Server%2FDatabaseStatus&state=123&login=true&scope=openid) contains a parameter redirect_uri with value {myDomain}%2FFROST-Server%2FDatabaseStatus.

This leads to a 404-Message: The requested resource [/FROST-Server/FROST-Server/DatabaseStatus] is not available

Changing redirect_uri to http%3A%2F%2F{myDomain}%2FDatabaseStatus leads to 403 Forbidden.

I think the redirect_uri interferes with our rewrite from / to /FROST-Server in our Ingress. Could it be, that the "redirect-rewrite-rules"-Parameter has to be adjusted accordingly (see https://www.keycloak.org/docs/latest/securing_apps/#_java_adapter_config)?

@hylkevds
Copy link
Member

You could try doing the auth procedure with the browser-debugger open, so you can see what keycloak actually redirects to. Then you can see if the problem is in keycloak, or in the ingress configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants