jhipster-registry: Administration Options + UAA Incompatible

Overview of the issue

With non-UAA services, when I view any of the pages under the Administration dropdown (Metrics, Health, Config, Logs), it works beautifully. Great work - I’m impressed with what it can do! It’s a much improved microservice workflow.

With UAA services, when I choose the service from the dropdown, I receive a 401 error triggering the interceptor and am logged out.

Reproduce the error

Start the registry and a UAA.
Navigate to any choice under the Administration dropdown
Choose the UAA service in the dropdown
- You will be logged out and the only option in the navbar is to go home and login.

JHipster Version(s)

v4.5.3 of generator-jhipster (master) v3.0.1 of jhipster-registry

JHipster configuration

Default UAA

Click to see config

{
  "generator-jhipster": {
    "promptValues": {
      "packageName": "com.mycompany.myapp",
      "nativeLanguage": "en"
    },
    "jhipsterVersion": "4.5.3",
    "baseName": "uaa",
    "packageName": "com.mycompany.myapp",
    "packageFolder": "com/mycompany/myapp",
    "serverPort": "9999",
    "authenticationType": "uaa",
    "hibernateCache": "hazelcast",
    "clusteredHttpSession": false,
    "websocket": false,
    "databaseType": "sql",
    "devDatabaseType": "h2Disk",
    "prodDatabaseType": "mysql",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": "eureka",
    "buildTool": "maven",
    "enableSocialSignIn": false,
    "jwtSecretKey": "e3a02c2ac15a706364ec28e0c52bc90967e92131",
    "enableTranslation": true,
    "applicationType": "uaa",
    "testFrameworks": [],
    "jhiPrefix": "jhi",
    "skipClient": true,
    "nativeLanguage": "en",
    "languages": [
      "en"
    ],
    "clientPackageManager": "yarn"
  }
}

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 1
Comments: 27 (15 by maintainers)

Commits related to this issue

implement client credentials flow for management endpoints to UAA microservices fix #148 — committed to xetys/jhipster-registry by xetys 6 years ago

Most upvoted comments

For me the solution would be to add UAA token support to the Registry. It’s probably not very hard, as the Registry is in fact a JHipster application, so you would need to copy the security config of a working application and port it to the Registry.

jdubois on Mar 1, 2018

This is solved for OpenID Connect - I don’t know UAA well enough, but now that should be easier (and @xetys I can help)

jdubois on Oct 27, 2017