Closed tschannik closed 2 years ago
I did a little more digging and found out that the problem has something to do with the "uma2-configuration" endpoint. nestjs-keycloak-admin tries to fetch the following url:
https://keycloakurl/auth/realms/master/.well-known/uma2-configuration
This endpoint returns a 404 on my keycloak server.
If i query
https://keycloakurl/realms/master/.well-known/uma2-configuration
i am getting a useful result. It is also documented here Is this a missconfiguration on my server or a problem with the package?
Thank you for this great finding! Community salutes you! It seems keycloak changed its API routes in the latest version. It's our mistake. Can you open a pull request?
curl -X GET \
http://${host}:${port}/realms/${realm}/.well-known/uma2-configuration
I fixed and released a version.
Hi,
I just tried to replace the nest-keycloak-connect library with your one. Unfortunately with the same settings i'm getting an error on startup with very limited information.
I tried to reproduce the issue with the example backend there seems to be some issues with it.
In the following screenshots you can see all logs I'm getting:
I'm happy to provide more information if nessessary.