-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Unexpected type of JSON object member with key mtls_endpoint_aliases #174
Comments
Oh, I think it's because we didn't upgrade this project, to match with Keycloak 15 |
@pascalgrimaud : I can take this one |
Increasing the bounty |
Is somebody working on it? |
@DDOUP I was working on it but I didn't have time to continue for the moment. You can take the issue if you want ? |
The solution is simple. In my case the dependency org.springframework.security.oauth::spring-security-oauth2 imported the dependency com.nimbusds::oauth2-oidc-sdk , but a very old version of it, 6. something. I'm not aware of your project structure here, because I just stumbled accross this thread, but if you are using Maven, just do the following: Update the version of com.nimbusds::oauth2-oidc-sdk in your dependencyManagement tag to version 9.22.2. Or just import the new version in your dependencies tag. Then you should be good to go! |
@Walnussbaer Thank you for your help ! I will try your solution. The other thing is that we have to update the whole application to get all JHipster dependencies. |
You are welcome, I'm curious whether it works out for you too! |
The problem is in the incompatibility between minbus-jose-jwt 7.1 and the 9.15. Specifically, the call to the json parser in 7.1 is an JsonObject: in 9.15 is a map: So, minbus-jose-jwt 9.15 and spring-security-oauth2-jose 5.2.2.RELEASE are incompatibility. The solution is using the the 5.4.5 of spring-security-oauth2-jose. Here the dependencies to add to the pom: org.springframework.security spring-security-oauth2-jose 5.4.5 com.nimbusds oauth2-oidc-sdk 9.15 runtime |
@fchiri Tried your answer and it was on spot |
@Walnussbaer Thanks for the help. com.nimbusds.oauth2.sdk.ParseException: Unexpected type of JSON object member with key "mtls_endpoint_aliases" this issue is ressolved as I updated the nimbusds to the 9.34 |
As Great Thanks! @[Walnussbaer] (https://github.com/Walnussbaer) It worked. |
spring-security-oauth2-jose 5.4.5 (https://mvnrepository.com/artifact/org.springframework.security/spring-security-oauth2-jose/5.4.5) depends on nimbus-jose-jwt 8.20.2, in which the spring-security-oauth2-jose 5.5 depends on nimbus-jose-jwt 9.8.1, in which the And I recommend using com.nimbusds oauth2-oidc-sdk 9.4, which happens to depend on nimbus-jose-jwt 9.8.1 as well.
|
When trying to launch the control center via
docker-compose
, the following error is displayed:The top of the stack trace is misleading, because I was thinking the container couldn't reach the keycloak container. After adding a delay, connecting, and running curl, it definitely can connect:
Further down the stack trace:
I think this could be similar to: jhipster/generator-jhipster#15836 (comment)
The text was updated successfully, but these errors were encountered: