SSO / SAML
Full Fabric supports enterprise single sign-on (SSO) via SAML 2.0. When enabled, users authenticate through their organisation's identity provider (IdP) — such as OneLogin, Okta, or Microsoft Entra ID — instead of entering a Full Fabric password. This centralises credential management and integrates Full Fabric into the institution's existing identity infrastructure.
How SAML Authentication Works
Full Fabric uses SP-initiated SAML only — the login flow always starts from the Full Fabric login page. IdP-initiated flows (where the user starts from the identity provider's portal) are not supported.
- User visits the Full Fabric login page and clicks "Institutional Login" (or is redirected automatically if SAML is the only auth method).
- Full Fabric sends a signed SAML Authentication Request to the IdP.
- The user authenticates at the IdP (entering their institutional credentials).
- The IdP sends a signed SAML Response back to Full Fabric's callback URL.
- Full Fabric validates the response, extracts user attributes, and creates a session.
SAML-Only Mode
When SAML is the only enabled authentication method (no social login or native password), the login page skips the email entry step and redirects directly to the IdP. Logout also triggers a SAML Single Logout (SLO) request to the IdP.
Profile Matching
When a SAML response is received, Full Fabric looks up the user by a configurable attribute (typically email). If a matching profile is found, a session is created. If no match is found and the IdP provides the required attributes, a new profile is automatically created and activated.
Where Continue sends each person
The login page asks for an email address first. When the person clicks Continue, Full Fabric goes down the institution's list of sign-in methods under Settings → Authentication, in the order staff drag them into, and sends the person to the first one that applies to them:
| Method | Applies when |
|---|---|
| A SAML provider | the address's email domain is one the provider lists, or one of the person's lifecycle states is one it lists |
| Email and password | always: the person gets the password field, an emailed sign-in link or sign-up, so nothing listed below it is reached |
| the address has no account yet, or one that never finished signing up, and self-registration is on (they sign up through Google), or the account is linked to a Google account (it has signed in with Google before), has no password and is not staff | |
| the address has no account yet, or one that never finished signing up, and self-registration is on (they sign up through LinkedIn), or the account is linked to a LinkedIn account, has no password and is not staff |
If nothing applies, the page does what it always has: a passwordless account is emailed a sign-in link, and an address with no account is offered sign-up.
The order of the list matters. Every tenant starts with email and password first, then every SAML provider, then Google, then LinkedIn, so nobody is redirected anywhere until staff drag a provider above email and password. A new SAML provider is added after the last SAML provider. Put a method higher to make it win for the people it applies to.
- Only a usable method counts: enabled and configured (for SAML, the IdP SSO target URL, the IdP certificate and the user lookup key).
- Google and LinkedIn apply to new sign-ups (an address with no account, or one that never finished signing up) and to active accounts without a password, never to staff, so a person with a password is never sent to them even when they are listed first.
- Google and LinkedIn register new people only when listed above email and password, and only while self-registration (the
auth.identity.registrationssetting) is on. A SAML provider creates the account on first sign-in whatever that setting says, since the identity provider vouches for the person. - Google signs in whichever Google account the person picks there; the typed address only preselects it.
- A suspended, scrubbed or anonymized account keeps its own message; only a domain match routes it.
- Routing switches no method off, but Continue always sends a matched person to the same place. They reach another method through its own button ("Log in with SSO", Google, LinkedIn) or, for the password field and emailed links, only once the method they were sent to fails and is skipped (see below).
- What Continue answers depends on the account, so it can tell someone typing an address more than whether it exists: that it is in a listed lifecycle state, or linked to Google or LinkedIn.
When a method refuses
If the method a person was sent to returns a failure (the IdP rejects the sign-in, they cancel at Google, their linked account is suspended), that browser skips it on the next Continue and is sent to the next method in the list that applies. The skip is remembered per browser, not per person, for ten minutes or until the next successful sign-in, so an identity provider that was briefly down is tried again. A failure the identity provider shows on its own pages, without ever returning to Full Fabric, cannot be seen, so it is not skipped.
The email is passed along
When the person has already typed their address, it is passed to the identity provider so its sign-in can be prefilled:
- SAML: sent as a
login_hintparameter on the sign-in request. Microsoft Entra honours it; identity providers that do not support it ignore it. - Google: sent as Google's
login_hint, which preselects the account. - LinkedIn has no equivalent.
The same happens when the person clicks a "Log in with SSO" link or the Google button after typing their address.
Email domains
List the domains whose addresses belong to a SAML provider, for example school.edu.
- Matching is exact and ignores case:
jane@School.EDUmatchesschool.edu, butjane@alumni.school.edudoes not. List each subdomain on its own. - A domain belongs to one provider. Saving a domain another SAML provider already lists is refused, naming that provider.
- A domain matches whether or not the address has an account (SSO creates the profile on first sign-in).
Lifecycle states
Pick whole lifecycle states under Lifecycle states: any state except user and admin, so prospect, applicant, student, alumnus, staff, contact and lecturer. Substates cannot be picked; a state covers all of its substates.
- A person matches when any of their roles, in any context, is in one of the states. Withdrawn roles do not count.
- Several providers may list the same state; the first in the list wins.
- Matching follows the person's current states at each Continue.
Example. Campus SSO lists the domain school.edu and Student SSO lists student. Jane is jane@school.edu, an enrolled student.
- With email and password first (the default), she gets the password field, or an emailed link or sign-up, like everyone else.
- Drag Campus SSO to the top and Continue sends her to Campus SSO; drag Student SSO above it and she goes to Student SSO.
- Either way she can still use any of them.
Institution Configuration
SAML is configured per institution through the settings interface. The following settings are required:
| Setting | Description |
|---|---|
auth.saml.enable |
Enable or disable SAML authentication |
auth.saml.idp_sso_target_url |
IdP login URL (SAML 2.0 Endpoint) |
auth.saml.idp_slo_target_url |
IdP logout URL (Single Logout endpoint) |
auth.saml.idp_entity_id |
IdP entity identifier (Issuer URL) |
auth.saml.idp_cert |
IdP's X.509 certificate (for validating SAML responses) |
auth.saml.sp_cert |
Full Fabric's SP certificate (public key) |
auth.saml.sp_private_key |
Full Fabric's SP private key (for signing requests) |
auth.saml.user_key |
Profile field for user lookup (e.g., "email") |
auth.saml.mappings |
Attribute mappings from IdP to profile fields |
Optional Settings
| Setting | Description |
|---|---|
auth.saml.skip_recipient_check |
Bypass SAML recipient validation (useful for testing) |
auth.saml.debugging |
Enable SAML response logging for troubleshooting |
Attribute Mapping
SAML attribute mappings define how IdP attributes translate to Full Fabric profile fields. Mappings are configured as source/target pairs:
| Source (IdP attribute) | Target (Full Fabric field) |
|---|---|
email |
email |
first_name |
first_name |
last_name |
last_name |
Additional custom attributes can be mapped depending on the IdP configuration.
Certificate Management
Generating SP Certificates
Full Fabric requires an SP certificate pair (public certificate + private key) for signing SAML requests and decrypting encrypted assertions.
To generate a certificate pair:
ssh-keygen -t rsa -b 4096
openssl req -out certificate.csr -key sp -new
openssl req -x509 -sha256 -days 3650 -key sp -in certificate.csr -out certificate.pem
The generated certificate (certificate.pem) goes into the auth.saml.sp_cert setting, and the private key into auth.saml.sp_private_key.
Encrypted Assertions
If the IdP supports encrypted assertions (recommended for production), paste the SP public certificate into the IdP's configuration. The IdP will encrypt assertions using this certificate, and Full Fabric will decrypt them using the private key.
Signature Details
Full Fabric signs SAML AuthnRequests and Logout Responses using RSA-SHA1 with a SHA1 digest. The SP metadata is also signed. Both the sp_cert and sp_private_key settings are required for request signing.