Closed zhennTil closed 4 years ago
Nevermind -- it seems like there's deeper issues... looking further into it...
It seems like not setting the name field on the ClientScopeRepresentation made Keycloak bug out -- at least on Keycloak 7.0.0, maybe not 4.8.3.
Furthermore, it seems like the controller was intended to set the name rather than the UUID of the client scope. This change lets Keycloak assign the UUID instead.
The
ClientScopeResource
Java class uses aMap<String,String>
for theattributes
field, but the CRD defines it as an array of key/value pairs. Thus, defining theattributes
field in a client scope resource causes keycloak-controller to fail.This changes the CRD to define
attributes
as an object rather than an array.