4:26 a.m.
Hi,
Sorry to ask again, but no one answered.
Any way to work with a single /certs URL for all realms?
Any way to configure all realms to use the same keys?
Regards,
Ori.
-----Original Message-----
From: keycloak-user-bounces(a)lists.jboss.org <keycloak-user-bounces(a)lists.jboss.org>
On Behalf Of Ori Doolman
Sent: Thursday, November 7, 2019 10:22 PM
To: keycloak-user(a)lists.jboss.org
Subject: [keycloak-user] Multi-tenant system: Using single /certs endpoint for all realms
(spring-security-oauth2)
Hi,
I'm using spring-security-oauth2-autoconfigure package in my Spring boot Java service
for securing my REST endpoints. I'm not using any Keycloak adapters. It's
basically working, but there is a problem with multi-tenancy (multi realms).
I'm getting the Keycloak token in the Authorization header, and then the spring code
is using a class named JwkTokenStore (and other related ones) to verify the token
signature.
For that, it is getting the public key from Keycloak by interrogating the /certs
endpoint.
In keycloak, each realm has its own public key (represented by different KID) and also its
own /certs endpoint.
For example, if I have 2 tenants on my system, then my service will have to interrogate 2
endpoints:
/auth/realms/{tenant1}/protocol/openid-connect/certs
/auth/realms/{tenant2}/protocol/openid-connect/certs
This poses an issue, since it means I will have to interrogate another endpoint each time
I add another tenant to my system.
And unfortunately, spring-security-oauth2 does not support dynamic discovery of new public
key endpoints. It can only use the ones provided upon startup.
It means I have no way to support dynamic on-boarding of new tenants.
My questions:
1) Is there any way to configure Keycloak to use a single /certs endpoint for all the
realms (and return the KIDs of all realms)?
Or maybe have all realms share the same keys between them and then I will always use the
master realm endpoint.
2) Why different realms must use different keys in Keycloak? I suppose the answer would
involve the term "security" : ) But still, when using Google APIs, all
customers are using the same public key from this URL:
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.googleapis.com_o...
.
Thanks,
Ori.
----------------------------------------------------------------------
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise
protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it
by any means. Please delete it and any attachments and notify the sender that you have
received it in error.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.jboss.org_mail...