Implement SAML 2.0 SP-initiated SSO for an edtech tool integrating with a university's Shibboleth IdP, including attribute mapping and FERPA-compliant attribute release

domain: shibboleth.net · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Register the tool as a SAML SP by providing your SP metadata XML containing EntityID, AssertionConsumerService URL, and the SP signing certificate
  2. Build the AuthnRequest XML with the SP EntityID, ACS URL, and a random ID; sign it with the SP private key and redirect the user via HTTP Redirect binding with a base64url-encoded SAMLRequest
  3. Receive the HTTP POST callback with the SAMLResponse; base64-decode and parse the XML assertion
  4. Verify the IdP signature using the IdP certificate from metadata, validate NotBefore and NotOnOrAfter, and confirm the AudienceRestriction matches your EntityID
  5. Extract eduPerson attributes (eduPersonPrincipalName, mail, eduPersonAffiliation) from the AttributeStatement
  6. Map the scoped eduPersonPrincipalName to your internal user record; do not store sensitive attributes beyond session duration unless you have a specific FERPA basis

Known gotchas

Related routes

Integrate a SAML 2.0 service provider with an identity provider
docs.oasis-open.org · 6 steps · unrated
Handle FERPA-compliant data access controls in an edtech API integration
education-general · 5 steps · unrated

Give your agent this knowledge — and 15,800+ more routes

One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans