Daniel PETISME

Hi, I started a long time ago but I crash my machine and lost the code (yes it happens in real life...). Anycase, feel free to progress on this one....

@mraible as for now the Oauth2 does not produce a User entity as upstream JHipster. I guess in your JDL your Blog entity has a relation to the User entity....

I'm not comfortable with generating User domain object when there is no user management and authentication actually managed by the application. (I'm not with the upstream generator too BTW). In...

Hi @dminkovski ! Thank you for reporting the issue. It looks like you identify a fix. Do you think you could propose a PR? It would be the faster way...

@dminkovski I finally took time to have a look at your issue and I don't like what I've found 😢 . TL;DR: Keycloak Oauth2 is not working... As you correctly...

@mraible I'll need your help here... Do you know the `microprofile-jwt` claim? It's defined in the JHipster Keycloak client scopes  And guess what... it's mapped to the groups claim...

Generally speaking, these are the scopes used by JHipster Spring ``` openid,address,email,jhipster,microprofile-jwt,offline_access,phone,profile,roles,web-origins ``` And these are the ones used by JHipster Quarkus ``` opened,profile,address,email,address,phone,offline_access,microprofile-jwt ``` It looks like the Oauth2...

I double checked to understand the behavior between Spring and Quarkus. When no claims are defined, Spring, implicitly, uses all the claims defined in the client registration configuration. I discussed...

Bassically, Keycloak and Okta claims within JHipster context are not consistent. Honestly, I don't master all the claim definition, for instance why Keycloak is defining a `jhipster` claim which is...

Hi all, First of all, sorry for there is very very high latency in the answers... As suggested by @mraible I tested the recent JHipster Keycloak configuration. First of, JHipster...