Share these parameters with your Relying Party (Service Provider) such as AWS IAM, Okta, Azure AD, Auth0, Google Workspace, or custom SAML applications.
Upload idp-metadata.xml when creating an Identity Provider in AWS IAM. Select the AWS IAM preset from the top dropdown for Role and RoleSessionName attributes.
Select the W3C DBSC preset or enable the DBSC & Advice section in the SAML Response form to assert device bound public key digests (dbsc:TrustedKey) and certificate fingerprints.
Set entryPoint: 'https://fake-saml-idp.pages.dev/', issuer: 'https://fake-saml-idp.pages.dev/saml/idp', and upload or paste the certificate PEM.
If your Service Provider asks for SLO or Change Password URLs, configure https://fake-saml-idp.pages.dev/logout and https://fake-saml-idp.pages.dev/change-password.
SAML 2.0 Response
Pre-populated with sensible defaults. Configure identity, attributes, DBSC, keys, and submit response to the Service Provider.
| Attribute Name | Format | Values | Action |
|---|
Assert cryptographic key digests and certificate fingerprints bound to the user's client device per the W3C DBSC specification (xmlns:dbsc="https://www.w3.org/ns/dbsc/saml") formatted as unpadded Base64URL.
Signatures are generated using standard RSASSA-PKCS1-v1_5 with SHA-256 and W3C Exclusive Canonicalization.
Generating SAML Response...
Loading metadata...