Ensure social-auth raises exceptions caused by incorrect configurations with Keycloak
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 4
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 114
Description
User Story
As an application administrator, I want to ensure that any errors raised during authentication with Keycloak are raised and visible in Sentry.
As a user, I expect to see a login-error page.
Description/Context
If there is an incorrectly configured client application setup in Keycloak, errors occurring within the client application as part of the login workflow should be visible in Sentry.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the Keycloak authentication workflow and how client-application errors are handled; done means configuration errors are visible in Sentry while users reach a login-error page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100