Skip to content

Add trusted providers section to OAuth documentation#1947

Closed
martinoak wants to merge 1 commit into
statamic:6.xfrom
martinoak:patch-3
Closed

Add trusted providers section to OAuth documentation#1947
martinoak wants to merge 1 commit into
statamic:6.xfrom
martinoak:patch-3

Conversation

@martinoak

@martinoak martinoak commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

In release 6.24.2 and 5.74.1, a new trusted_providers config has been implemented. Since we use custom OAuth2 provider, people couldn't login into the Control Panel without adding the trusted_providers array with our provider in it.

Feel free to rewrite the docs, I just wanted to pointed out that this section is missing in the docs.

Related: #1946

Added instructions for using trusted providers with custom OAuth providers.
@jasonvarga

Copy link
Copy Markdown
Member

@martinoak Logging in should've required no changes.

The only thing that would've changed would have been trying to logging into an existing Statamic account with an OAuth provider that was not already linked to the Statamic user.

Are you using v5 or v6?

@martinoak

Copy link
Copy Markdown
Contributor Author

@jasonvarga still on v5, we use our own company provider, but since the user wasnt even in the file that stores oauth id with our provider's identifier. When I added trusted_providers array key, everything worked even on clean installations.

@jasonvarga

Copy link
Copy Markdown
Member

But when the user tried to log in with your company OAuth for the first time, was there already a Statamic account with that same email?

@martinoak

Copy link
Copy Markdown
Contributor Author

Yes, otherwise "Unauthorized" message would appear.

@jasonvarga

Copy link
Copy Markdown
Member

Cool cool, thanks. Addressed in c3b2919 for the v5 subdomain.
Equivalent for v6 coming shortly.

@jasonvarga jasonvarga closed this Jul 14, 2026
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.

2 participants