More OAuth identity providers
Applications can offer additional provider sign-in options from the connection catalog.
From the changelog: More OAuth identity providers
Authdog Team
Hosted sign-in is only as useful as the buttons on it. The connection catalog now includes more OAuth identity providers, so applications can offer the accounts users already have without a custom callback for each vendor.
This is the longer note behind the July 4 changelog entry.
How it works
These providers join the existing social connections:
- Intuit
- Vercel
- Xero
- Coinbase
- DocuSign
- GitLab
- Naver
Each entry ships with a provider recipe, an icon for the hosted button, and tested callback handling. You enable them per environment next to Google, GitHub, and the rest of the catalog. The application still sees one normalized Authdog session after the callback.
Set it up
In the Authdog console, open Authentication > Providers:
- Select the project and environment.
- Enable the provider from the catalog.
- Follow the recipe for that vendor's client ID, secret, and redirect URI.
- Save, then complete a sign-in on the hosted Account Portal.
Use the callback URL Authdog displays for that environment. A mismatch with the vendor app registration is the usual cause of a failed return.
Trust boundaries
OAuth sign-in proves the user completed that provider's consent. It does not grant roles in your app. Map groups or roles separately, and keep enterprise SSO on the enterprise connectors when the customer requires SAML or IdP-initiated login.
Provider credentials are environment-scoped. A client configured in dev does not authenticate prod.
Try it
The catalog lives on Integrations. The original release note is in the changelog.