You’re offline. This is a read only version of the page.
4
You're absolutely right — integrating Login.gov as a SAML identity provider with Power Pages is not straightforward due to Login.gov’s strict SAML requirements, particularly around the AuthnContextClassRef attribute.
Power Pages' out-of-the-box SAML 2.0 provider setup does not expose a way to customize the SAML request payload, including the AuthnContextClassRef, which Login.gov requires to be explicitly set (e.g., urn:oasis:names:tc:SAML:2.0:ac:classes:IAL2).
Microsoft officially supports using Azure AD B2C with custom policies (IEF) to integrate with Login.gov. This allows you to:
Share
Report
All responses (
Answers (
AuthnContextClassRef.Once configured, you can connect Power Pages to Azure AD B2C (which then federates to Login.gov).
Microsoft’s GitHub repo has a Login.gov + Azure AD B2C sample .
As of now, Power Pages does not support customizing the SAML AuthN request directly. The /Account/Login/ExternalLogin endpoint is managed internally and does not allow injection or override of the AuthnContextClassRef.
The site you referenced (oscportal.powerappsportals.us) may be:
If you're open to it, I can help you:
