SSO Integration Options

AlumnIQ supports multiple federation patterns so institutes can use their existing campus identity systems.

Supported protocols and AlumnIQ role

• SAML 2.0: AlumnIQ acts as the Service Provider (SP) and your institution provides an Identity Provider (IdP).
• OAuth 2.0: AlumnIQ acts as the OAuth client and your institution provides the Authorization Server / IdP.
• OpenID Connect (OIDC): AlumnIQ acts as the OIDC client (Relying Party) and your institution provides the OIDC Provider / IdP.

Requesting federation setup

To request an SSO integration, email helpdesk@alumniq.com and include:

1. Your institution name and AlumnIQ environment(s) to configure (for example: production, qa, platform, signature).
2. The protocol you want to use: SAML 2.0, OAuth 2.0, or OIDC.
3. A technical contact from your identity team.
4. Target timeline or launch date.

After the request is opened, AlumnIQ will coordinate with your identity team to exchange required connection details and complete test validation.

Required identity and mapping agreement

For your chosen protocol, we will need your institutional IdP/Provider details and we must agree on a stable user identifier claim/attribute used to map users in AlumnIQ. For SAML, this identifier is typically mapped to uid in our SP attribute map.

Typical examples include:

• SAML attribute/NameID mapped to uid (for example, urn:oid:1.3.6.1.4.1.5923.1.1.1.6, urn:oid:0.9.2342.19200300.100.1.1, universityid, or NameID format urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress)
• OAuth/OIDC claim (for example, sub or another agreed institutional identifier)

The key requirement is that the value be stable (preferably immutable) and unique so each authenticated user can be reliably matched to the correct AlumnIQ identity.