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
Describe the bug
when running CN upgrade to latest config-api 1.0.4 snapshot, config-api creates missing scopes
this work flawlessly when there is 1 instance/replica of config-api
but when there are 2 replicas running at the same time, each config-api creates same scope (based on jansId)
To Reproduce
Steps to reproduce the behaviour:
Restart multiple config-api instance
On start-up error is displayed
Error jakarta.ws.rs.WebApplicationException: Multiple Scope with same name - https://jans.io/oauth/config/agama.write Expected behaviour
all confi-api instance should start without error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
-NA
Smartphone (please complete the following information):
NA
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
when running CN upgrade to latest config-api 1.0.4 snapshot, config-api creates missing scopes
this work flawlessly when there is 1 instance/replica of config-api
but when there are 2 replicas running at the same time, each config-api creates same scope (based on jansId)
To Reproduce
Steps to reproduce the behaviour:
jakarta.ws.rs.WebApplicationException: Multiple Scope with same name - https://jans.io/oauth/config/agama.write
Expected behaviour
all confi-api instance should start without error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
-NA
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: