-
-
Notifications
You must be signed in to change notification settings - Fork 657
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
OAuth2 authentication betwwen registry and gateway #338
Comments
If I understand this issue correctly, I believe it might be happening because JHipster Registry does not include global OIDC logout. Is that you can't log out of the registry the main issue? |
No, my main issue is about I have to be logged in gateway to get metrics and/or configuration of gateway from registry. I guess that the problem of logout gateway / registry is a consequence of this. There is another problem I did not talk here because I cannot reproduce at each time. Sometimes, when I start a service after I log in registry, I cannot get its metrics/configuration. I have to disconnect and reconnect for this. |
I mentioned the gateway login requirement here, I'm not sure of how to fix it though. |
jhipster info for the gateway :
JHipster Version(s)
JHipster configuration, a
.yo-rc.json
file generated in the root folder.yo-rc.json file
JDL for the Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryJDL entity definitions
Environment and Tools
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
git version 2.17.1
node: v9.0.0
npm: 5.5.1
yarn: 1.7.0
Docker version 18.09.2, build 6247962
docker-compose version 1.17.1, build unknown
Overview of the issue
This issue concerns authentication between registry and gateway with keycloak. We have to be authenticated on gateway and registry to view configuration or metrics of gateway in registry.
Motivation for or Use Case
Authentication between registry and gateway is unstable with keycloak. In some cases, registry send a 401 error on /login...
Reproduce the error
Related issues
This issue may be related to issue 292 OAuth2 Gateway Management Broken
Suggest a Fix
I don't know if the problem comes from gateway or registry, and I don't known enough OAuth2 to suggest a fix.
JHipster Registry Version(s)
Gateway has been generated with jhipster 5.8.2, and registry is in version 4.1.1
Browsers and Operating System
Tested on linux with firefox 65 and chromium 73
Denis
The text was updated successfully, but these errors were encountered: