You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using nest-keycloak-connect to integrate Keycloak into my NestJS app, and I’ve hit a roadblock. My Keycloak server is set up with a self-signed certificate, and when the app tries to validate access tokens, I keep getting this error:
It looks like the library doesn’t trust the self-signed certificate, and I haven’t found an easy way to configure it to work. I’ve tried adding the realmPublicKey directly in the configuration, which I assumed would bypass SSL verification, but the issue persists.
It would be super helpful if there was an option in the library to allow self-signed certificates (at least for dev setups) or better documentation on how to handle them.
Any chance of adding support for this or pointing me in the right direction? Let me know if more details are needed—happy to provide more info if it helps!
The text was updated successfully, but these errors were encountered:
I’m using nest-keycloak-connect to integrate Keycloak into my NestJS app, and I’ve hit a roadblock. My Keycloak server is set up with a self-signed certificate, and when the app tries to validate access tokens, I keep getting this error:
[Nest] 1 - 01/15/2025, 4:28:29 PM WARN [Keycloak] Cannot validate access token: Error: self-signed certificate
It looks like the library doesn’t trust the self-signed certificate, and I haven’t found an easy way to configure it to work. I’ve tried adding the realmPublicKey directly in the configuration, which I assumed would bypass SSL verification, but the issue persists.
It would be super helpful if there was an option in the library to allow self-signed certificates (at least for dev setups) or better documentation on how to handle them.
Any chance of adding support for this or pointing me in the right direction? Let me know if more details are needed—happy to provide more info if it helps!
The text was updated successfully, but these errors were encountered: