Skip to content

Conversation

@shaharb13
Copy link

PingFederate now uses an Identifier-First authentication flow where the username/email is entered on a separate page before the password. This change adds support for:

  • Identifier-First flow detection and handling (input[name="subject"])
  • Duo Security plugin form detection and submission
  • Duo MFA push notification flow with status polling
  • Auto-POST form detection for redirect callbacks
  • Improved meta refresh handling to follow actual redirect URLs

The Identifier-First flow works as follows:

  1. User enters email/username on first page
  2. Server returns password page
  3. User enters password
  4. MFA flow (Duo) if configured
  5. SAML assertion returned
PingFederate now uses an Identifier-First authentication flow where
the username/email is entered on a separate page before the password.
This change adds support for:

- Identifier-First flow detection and handling (input[name="subject"])
- Duo Security plugin form detection and submission
- Duo MFA push notification flow with status polling
- Auto-POST form detection for redirect callbacks
- Improved meta refresh handling to follow actual redirect URLs

The Identifier-First flow works as follows:
1. User enters email/username on first page
2. Server returns password page
3. User enters password
4. MFA flow (Duo) if configured
5. SAML assertion returned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants