title: jhipster-registry with oauth2 - eureka and config endpoints unsecured?
body: <p>Is it correct that the eureka and config endpoints provided by the jhipster-registry are not secured or am I doing something wrong?</p>
  
  <p>I started the jhipster-registry (latest docker image) with oauth2 profile and a keycloak configuration. When I try calling the eureka/apps REST endpoint without basic authentication I get the login page html of keycloak - that's ok. If I send the basic authentication header I always get a result - even if I send it empty or with a user that does not exist.</p>
  
  <p>Is this the intended behaviour or am I missing some configuration?</p>
  
  <p>Thanks!
  Kristina</p>