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 noticed an unhandled exception with status code 500 (Internal Server Error) during the deletion of assigned default client scopes:
"Exception":"Org.Eclipse.TractusX.Portal.Backend.Framework.ErrorHandling.ServiceException: Internal Server Error: http://sharedidp-keycloak/auth/admin/realms/master/clients/34e015a5-b944-46d8-a9f3-4bc8e856a727/default-client-scopes/ff556da8-6b2b-4fe3-97cf-4a9c93ffc3c1\n ---> Flurl.Http.FlurlHttpException: Call failed with status code 500 (Internal Server Error): DELETE http://sharedidp-keycloak/auth/admin/realms/master/clients/34e015a5-b944-46d8-a9f3-4bc8e856a727/default-client-scopes/ff556da8-6b2b-4fe3-97cf-4a9c93ffc3c1\n
Scenario:
master-realm is created and to default clients admin-cli, account and security-admin-console the default client scope acr is assigned
seeding job uses a json file for the master realm where the default client scope acr is not assigned to default clients admin-cli, account and security-admin-console
seeding job runs into the exception above BUT only after successfully removing the assignments of the default client scope acr from default clients admin-cli, account and security-admin-console
Why is this exception thrown if the deletion is successful?
After the seeding job ran into this error, it was running without error at the second run.
And I was able to avoid this error to begin with by adding the default client scope acr to the default clients admin-cli, account and security-admin-console.
I still think it's worth investigating this behaviour.
I've created a keycloak issue for that, the error occurs when using postman as well, it seems like it is a caching issue or something since the client-scope is removed but the api response is a 500
Description
Follow up on #910 (review)
I noticed an unhandled exception with status code 500 (Internal Server Error) during the deletion of assigned default client scopes:
Scenario:
admin-cli
,account
andsecurity-admin-console
the default client scopeacr
is assignedacr
is not assigned to default clientsadmin-cli
,account
andsecurity-admin-console
acr
from default clientsadmin-cli
,account
andsecurity-admin-console
Why is this exception thrown if the deletion is successful?
After the seeding job ran into this error, it was running without error at the second run.
And I was able to avoid this error to begin with by adding the default client scope
acr
to the default clientsadmin-cli
,account
andsecurity-admin-console
.I still think it's worth investigating this behaviour.
Additional Information
relates to #910
The text was updated successfully, but these errors were encountered: