SAML apps

SAML apps are the identity provider connections behind single sign-on. You define each one here, then select it from Web authentication or Apps authentication when configuring SSO.

Keeping them separate means one connection can serve several channels, and a certificate rotation is done once rather than in every place SSO is configured.

Where to find it

Open the Admin Console, then go to Leena Channels → SAML apps.

The page lists every app with its App name, Entity ID and Status:

StatusMeaning
LiveFully configured. Selectable during SSO setup, and its SP metadata can be downloaded
DraftSaved part-way. Not offered in the SAML app dropdowns on Web or Apps authentication until it goes Live

Each row's Actions menu offers Edit and, for Live apps, Download SP metadata — the file your identity provider needs to complete its side of the connection.

The SAML apps page with a SAML apps table showing App name, Entity id, Status and Actions columns and a Create new button

The SAML apps list

Creating an app

Click Create new. The Create a SAML app page opens with three sections, and nothing is stored until you save — leaving without saving creates nothing.

You can also start from Web or Apps authentication: Create SAML app at the top of the SAML app dropdown opens this page in a new tab.

SAML app details

FieldWhat it is
App nameRequired. The name used to identify this app, including when selecting it during SSO setup
Entity IDGenerated for you and can't be edited. Copy it into your identity provider's SP entity ID field. It stays the same for the life of the app

IDP configuration

If your identity provider gives you a metadata file, Upload IDP is the fastest route. Drag and drop an XML file or use Add file; it's read immediately and fills in the SSO URL and SSO certificate for you. The parsed values are stored when you save, along with the rest of the form. Only XML is accepted.

Don't have a metadata file to hand? Download sample IDP metadata, beside the upload area, shows the format expected.

FieldWhat it is
Accepted clock skew (ms)The largest time difference tolerated between your server and the IdP's clock. A whole number of milliseconds, 1 or more. 300000 ms (5 minutes) is recommended. Leave it blank to keep the stored value, or the 45-second default on a new app
SSO certificateRequired. The public X.509 certificate your IdP uses to sign assertions. Paste the full certificate, including the header and footer lines. Add more holds a further certificate
SSO URLRequired. The login URL your IdP provides to start SAML authentication. Must be an https URL
Signature algorithmsha1, sha256, or sha512. SHA-256 is recommended unless your provider requires otherwise
Identifier formatThe SAML NameID format your IdP sends — unspecified, emailAddress, entity, transient, persistent, encrypted, X509SubjectName, WindowsDomainQualifiedName, or kerberos

Holding more than one certificate is useful during a rotation: add the new certificate alongside the old one, switch the IdP over, then remove the old one.

⚠️

Fix clock drift rather than widening the skew

Timestamp validation is what stops an old assertion being replayed. If assertions are being rejected on timing, correct the clock drift first, and widen the skew only as far as you need.

Claim rule config

Claim rules map what your identity provider sends into the profile attributes Leena AI uses. Claim rules are optional; click Add claim rule to add one, up to a maximum of 10.

The lower part of the IDP configuration with SSO certificate, SSO URL, Signature algorithm and Identifier format, and Claim rule config with Identifier URL, Formatted name and Profile attribute fields and Add claim rule

IDP configuration and claim rules

FieldWhat it is
Identifier URLThe claim as your identity provider emits it
Formatted nameThe readable name for that claim
Profile attributeThe Leena AI profile attribute it populates

All three fields are required on any rule you add. Map only the attributes you actually use — every extra claim is another thing to keep in step when the provider's configuration changes.

Saving and testing

The page header carries three actions.

Save and test checks the whole form, saves the app as Live, and then offers a sign-in test: Test sign-in opens the app's sign-in flow in a new tab, or Skip for now to come back to it later. Test while you still have the metadata to hand, rather than discovering a certificate or URL problem when employees hit it.

Save as draft saves the app as Draft with only the App name filled in, and returns you to the list. Use it to park a half-finished connection.

⚠️

Save as draft on a Live app takes it out of SSO setup

Saving an existing Live app as a draft sets its status back to Draft, and it stops appearing in the SAML app dropdowns. For changes to a Live app, use Save and test.

Discard — or the SAML apps breadcrumb — asks you to confirm before leaving. Discard abandons your changes; No thanks keeps you on the page.

Editing an app

Choose Edit from a row's Actions menu. The page opens as Edit followed by the app's name, with the same three sections. The Entity ID can't be changed.


Did this page help you?