Repository navigation
Replies: 3 comments 8 replies
|
Just a note, this is using organizations. Not sure if anyone has dealt with this. |
|
Identified why this is happening. The service account user behind the client gets deleted and then re-created without all the original roles that we had added to it. It just gets re-created with default-roles- role. Not sure why it gets deleted, something we need to look into. But, this user should come up with the roles established in the client. Any thoughts on how to make the roles of a service account user persist? |
|
Seems to be something on our end, fixed now. |
|
Thanks for your fast response but unfortunately this is somewhat different from our setup. await adminClient.clients.update({id: client.id, realm: realm.id}, {
redirectUris: "https://foo.bar",
directAccessGrantsEnabled: true
});If I go through it step by step using the debugger, the roles are still assigned to the service account before this line. If I execute the line, the roles are no longer assigned to the service account and the UUID of the service account user is also different. Therefore I strongly assume that it has nothing to do with our code, because nothing else is executed than just this one line of code. |
|
hey, i got rid of the error by sending the entire client object when doing the PUT call |
|
I cannot remember beyond what I mentioned above. Sorry |
|
I faced a similar challenge where I experimented with sending different portions of the client object. Initially, I tried sending the entire object, which succeeded. Then, I gradually reduced the attributes I sent, and each attempt still worked seamlessly. However, the issue arose when I excluded the |
|
wanted to open an issue on that one, but i validated that against the latest version as of writing 26.2.4 and the issue appears to be resolved, i do only update the ... so i guess updating is the better option if you are able to |
Uh oh!
There was an error while loading. Please reload this page.
I have a Realm Created from a config on keycloak start up. It populates the database. This also creates a client with service account role assignments. This client is in the realm created at startup.
After an undetermined amount of time, the role assignments disappear. I re-add them, and they disappear again.
I cannot figure out how this is happening. Any help would be much appreciated.
Thanks
All reactions