Keycloak client rename — pal-e-docs-app to pal-e-app #255

New issue

Closed

opened 2026-03-30 22:03:31 +00:00 by forgejo_admin · 1 comment

forgejo_admin commented

2026-03-30 22:03:31 +00:00

Contributor

Type

Feature

Lineage

Standalone — scoped from pal-e-app project (project-pal-e-app).

Repo

forgejo_admin/pal-e-platform

User Story

As a stakeholder
I want to log in via Keycloak with clean redirect URIs
So that the auth flow works with the renamed pal-e-app deployment

Context

The Keycloak client in the pal-e realm is currently named pal-e-docs-app with redirect URIs pointing to pal-e-docs-app.tail5b443a.ts.net. This needs to be renamed to pal-e-app with redirect URIs updated to pal-e-app.tail5b443a.ts.net. The client is a public client using PKCE (no secret). Also update the pal-e-app frontend keycloak.ts to reference the new client ID.

File Targets

Files to modify:

Keycloak admin console — rename client or create new one
terraform/ — if Keycloak clients are managed via terraform

Files NOT to touch:

Westside Basketball Keycloak realm — different realm entirely

Acceptance Criteria

Keycloak client ID is pal-e-app in the pal-e realm
Redirect URIs include https://pal-e-app.tail5b443a.ts.net/*
PKCE (S256) still enabled, public client
pal-e-app frontend keycloak.ts updated with new client ID

Test Expectations

Manual: login flow works end to end
Manual: token refresh works

Constraints

Check if Keycloak clients are terraform-managed before making manual changes
Coordinate with namespace rename (sibling ticket)

Checklist

PR opened
Tests pass
No unrelated changes

project-pal-e-app
arch-deployment-pal-e-app

### Type Feature ### Lineage Standalone — scoped from pal-e-app project (project-pal-e-app). ### Repo `forgejo_admin/pal-e-platform` ### User Story As a stakeholder I want to log in via Keycloak with clean redirect URIs So that the auth flow works with the renamed pal-e-app deployment ### Context The Keycloak client in the pal-e realm is currently named pal-e-docs-app with redirect URIs pointing to pal-e-docs-app.tail5b443a.ts.net. This needs to be renamed to pal-e-app with redirect URIs updated to pal-e-app.tail5b443a.ts.net. The client is a public client using PKCE (no secret). Also update the pal-e-app frontend keycloak.ts to reference the new client ID. ### File Targets Files to modify: - Keycloak admin console — rename client or create new one - `terraform/` — if Keycloak clients are managed via terraform Files NOT to touch: - Westside Basketball Keycloak realm — different realm entirely ### Acceptance Criteria - [ ] Keycloak client ID is pal-e-app in the pal-e realm - [ ] Redirect URIs include https://pal-e-app.tail5b443a.ts.net/* - [ ] PKCE (S256) still enabled, public client - [ ] pal-e-app frontend keycloak.ts updated with new client ID ### Test Expectations - [ ] Manual: login flow works end to end - [ ] Manual: token refresh works ### Constraints - Check if Keycloak clients are terraform-managed before making manual changes - Coordinate with namespace rename (sibling ticket) ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `project-pal-e-app` - `arch-deployment-pal-e-app`

forgejo_admin referenced this issue

2026-03-30 22:10:10 +00:00

Namespace rename — pal-e-docs-app to pal-e-app in k8s and ArgoCD #257

forgejo_admin referenced this issue

2026-04-11 20:43:07 +00:00

Close stale pal-e-app / pal-e-docs-app rename tickets after pal-e-production landing #279

forgejo_admin referenced this issue

2026-04-11 20:57:21 +00:00

Close stale pal-e-app / pal-e-docs-app rename tickets after pal-e-production landing #279

forgejo_admin commented

2026-04-12 15:37:56 +00:00

Author

Contributor

Closing — both pal-e-docs-app and pal-e-app names are obsolete; canonical is pal-e-production. Forward-facing Keycloak work deferred under forgejo_admin/pal-e-platform#278.

Closing — both `pal-e-docs-app` and `pal-e-app` names are obsolete; canonical is `pal-e-production`. Forward-facing Keycloak work deferred under forgejo_admin/pal-e-platform#278.

forgejo_admin closed this issue

2026-04-12 15:37:57 +00:00