Repository navigation
Replies: 1 comment 1 reply
|
@ravthiru ,im facing similar issue.how didd you fix it? |
1 reply
|
Not able to extened CorsSpi, we ended up create a hack to override WebOriginsUtils.resolveValidWebOrigins |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Want to provide custom Cors implementation as Keycloak provided default implementation (DefaultCors) does not cater our requirement. There is no way to extend DefaultCors as the constructor is not public.
With latest keycloak 24 release , CorsSpi allows us to implement our own provider.
so tried using the code from DefaultCors and wrote custom Cors, by following Server Development documentation https://www.keycloak.org/docs/latest/server_development/#_providers.
Ended up creating following
a) CustomCorsProvider implementing Cors interface
b) CustomCorsFactory implementing CorsFactory with unique id and order as 1
c) added CustomCorsFactory entry in to META-INF/services/org.keycloak.services.cors.CorsFactory
but i could not see the my custom provider in the Keycloak UI Console and Keycloak is still going with DefaultCors.
Version of Keycloak Used 24.0.3
All reactions