Skip to content

fix(auth): stabilize provider resolution for CMS access maps#1798

Open
MrDirkelz wants to merge 1 commit into
mainfrom
cms-fix-dissapearing-permissions
Open

fix(auth): stabilize provider resolution for CMS access maps#1798
MrDirkelz wants to merge 1 commit into
mainfrom
cms-fix-dissapearing-permissions

Conversation

@MrDirkelz

Copy link
Copy Markdown
Collaborator

Prefer the persisted active provider when a matching Auth0 session cache exists, clear stale provider cache keys during login, and guard CMS startup from anonymous socket handshakes that can purge local content.

Add app parity tests and API warning coverage for provider-scoped group loss.

Prefer the persisted active provider when a matching Auth0 session cache exists,
clear stale provider cache keys during login, and guard CMS startup from anonymous
socket handshakes that can purge local content.

Add app parity tests and API warning coverage for provider-scoped group loss.
@MrDirkelz MrDirkelz linked an issue Jul 8, 2026 that may be closed by this pull request
const docOtherProvider = {
_id: "user-other",
_rev: "1-bbb",
email: "test@bccsa.org",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove domain specific data from test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CMS: Synced content being removed when refreshing at occasion

2 participants