URGENT: Revert PR #158 -- prod auth broken, Keycloak ROPC not configured #160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
bug
Lineage
standalone
Repo
ldraney/landscaping-assistant
User Story
As a user, I need to be able to log in to the app, which is currently broken because PR #158 deployed ROPC auth but Keycloak terraform was never applied.
Context
PR #158 replaced OmniAuth (Authorization Code flow) with Keycloak Direct Access Grants (ROPC). However, the Keycloak terraform was never applied, so Keycloak does not accept
grant_type=password. Production auth is completely broken.What Broke
Production login is completely broken. Users cannot authenticate because the app sends
grant_type=passwordto Keycloak, but Keycloak is not configured to accept Direct Access Grants.Repro Steps
Expected Behavior
Users should be able to log in via OmniAuth Authorization Code flow (redirect to Keycloak, get redirected back).
Environment
Production (Kubernetes)
File Targets
Acceptance Criteria
Test Expectations
Constraints
Checklist
af9dc69Related