Repository navigation
|
After authenticating on the Keycloak login screen, "401 Authorization Required" is displayed in the browser. WARN already used for userSession 'c1234567-bd4f-4e2a-9028-98d5fe5988eb' and client 'e1234567-300e-4550-ad47-2557d218e283'.
The system is configured on AWS. ALB - ECS(Fargate) - Aurora(postgreSQL 16.4) Keycloak is clustered. The reproducibility is not 100%. When the number of Keycloak tasks is reduced from two to one, the "401 Authorization Required" does not occur. I set Keycloak to debug mode. Search the logs of the authenticated Keycloak task using c1234567-bd4f-4e2a-9028-98d5fe5988ebSearch the logs of the Keycloak task that output WARN using c1234567-bd4f-4e2a-9028-98d5fe5988ebtaskDefinition "environment": [ |
Replies: 2 comments
If you haven't already read the docs, it would be good to review #23615 (reply in thread)
This points to a caching / discoverability issue - check the logs for what members appear in the cache cluster. If you see only one, then the servers are not finding each other. Double check that each instance is resolvable via hoge-prd-auth.hoge-prd-map-001. |
|
Thank you for your help. |
If you haven't already read the docs, it would be good to review #23615 (reply in thread)
This points to a caching / discoverability issue - check the logs for what members appear in the cache cluster. If you see only one, then the servers are not finding each other. Double check that each instance is resolvable via hoge-prd-auth.hoge-prd-map-001.