Skip to content

Added option for save OAuth testing with mock server #6348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
falcon027 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Added option for save OAuth testing with mock server #6348

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa22c54
Update social-authentication.mdx
falcon027 Jan 15, 2026
a92f4f1
fixed line brakes
falcon027 Jan 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 15 additions & 5 deletions docs/app/guides/authentication-testing/social-authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,15 +21,25 @@ description: Authenticate with common social authentication platforms with cy.or

<Icon name="exclamation-triangle" /> **Not recommended in CI**

Cypress does **not** recommend testing social connection authentication as a
primary means of authentication testing. This is due to the
Cypress does **not** recommend testing social connection authentication against **real providers** as a
primary means of authentication testing. This is due to bot detection, CAPTCHAs, and the
[challenges](/app/core-concepts/best-practices#Potential-Challenges-Authenticating-with-Social-Platforms)
mentioned in our
[Best Practices Guide](/app/core-concepts/best-practices).

Relying on social authentication in CI will likely result in bot detection and
in some cases, account suspension due to violating the provider's Terms of
Service.
**Recommended Alternative:**

To test the OAuth flow end-to-end without these issues, use the free and open source project
[oAuth mock server](https://github.com/atagon-GmbH/oAuth-mock).

By replacing your OAuth provider URL in development with [https://oauth.kogiqa.com](https://oauth.kogiqa.com), the server
will behave like a real OAuth provider (mimicking responses from Google, Facebook, etc.) but will
automatically accept requests and approve them. This is safe for use in CI.

You can customize the user scenario using query parameters:

- `?email=test@example.org`
- `&name=example`

:::

Expand Down