Before you start
- Administrator access to your Iru tenant.
A SplitSecure identity provider, created in a threshold vault and approved by its Guardian Team. See Create an identity provider.
A second browser profile, signed in to the Web App, for the test sign-in. Start and finish the test in that same profile.
This guide makes Iru a connected app of your SplitSecure identity provider, so an Iru administrator signs in only when your Guardian Team, the group of devices that together approve each proposal, approves it. You add SplitSecure as a custom SAML connection in Iru, then create the matching connected app.
Values you exchange
| Value | Where to find it | Where to paste it |
|---|---|---|
| SSO URL (HTTP-Post) | The identity provider’s SAML endpoints card in the Web App | Iru, Sign-In URL, in Create the custom SAML connection |
| Signing certificate (PEM) | The same card, Download Certificate → PEM format | Iru, Signing Certificate Upload, in the same step |
| Iru service provider metadata URL | Iru, Metadata, in Create the custom SAML connection | The Web App, Metadata Endpoint, in Create the connected app |
Add SplitSecure as a SAML connection in Iru
In the Iru web app
- Sign in to your Iru tenant.
- In the left sidebar, click your account, then Access.
- In the Authentication methods section, click + Authentication method.
- Give it a name (e.g.
SplitSecure), select SAML and click Next. - In Configuration Information, copy the URL under Metadata. It looks like
https://<subdomain>.id.iru.com/api/v1/federated-auth/<id>/saml/metadata. You paste it into the Web App in Create the connected app below.
Open the Web App in another tab to copy the values.
In the Web App, open Vaults, then your vault, then the identity provider. The SAML endpoints card shows three values:
- SAML IdP Entity ID
- SSO URL (HTTP-Redirect)
- SSO URL (HTTP-Post)
Under them, Download metadata XML saves the metadata file and Download Certificate offers the certificate in PEM format or DER format.
Fill in the form.
Field Value Sign-In URL The SSO URL (HTTP-Post)From the SAML endpoints card, not the SSO URL (HTTP-Redirect) Signing Certificate Upload The certificate fileDownload Certificate → PEM format on the card IdP attribute SubjectIru reads the user’s email from the NameID User attribute User Principal Name (UPN)The Iru value the email must equal Sign Request OnRecommended Sign Request Algorithm RSA-SHA256 Sign Request Algorithm Digest SHA 256 Protocol Binding HTTP-Post Click Save.
The connection appears in the Authentication methods section as Disabled. Click the ellipsis menu (⋮) on its right and select Enable.
Iru signs in only users it already knows, by email.
- In the left sidebar, click your account, then Access.
- In Admin and authentication section, click + Administrator.
- Enter the user’s information. UPN (User Principal Name) is the email that will be matched by the SplitSecure sign-in.
- Click Save. Iru sends the user an invitation email.
Connect Iru to SplitSecure
In the Web App
In the Web App, open Vaults, then your vault, then the identity provider. Click New Connected App and pick the service provider’s card. Name is required, and the Threshold Identity Provider field is fixed to this provider.
Click the Iru (SAML2) card.
Enter a Name, for example
Iru.Set the NameID. Iru matches each user by the email in the NameID, so the email SplitSecure sends must equal the user’s Iru email. Keep NameID format on Email Address.
Keep the default NameID value, Built from each person’s email. Its NameID template is
${user.email}, which SplitSecure fills with the email of the person who signs in. To accept only one email domain, enter it in Email must end with, for example@example.com. SplitSecure then refuses anyone whose email ends otherwise.In Metadata Endpoint, paste the URL from Metadata. It has the form
https://<subdomain>.id.iru.com/api/v1/federated-auth/<id>/saml/metadata.In Tenant name, enter the name in your Iru address,
https://<name>.iru.com. The Web App starts each sign-in at that address.Optionally, under Advanced Options, turn on Selective notifications so members can choose who gets notified for the Guardian Team’s proposals, set the Account Sensitivity banner shown on this connected app’s proposals (None, Low, Medium, High or Critical), and enter a Description or a Reason for creation.
Click Propose connected app. The Web App opens the proposal under Requests. The members of the Guardian Team approve it on their devices, in the mobile app. When the vote passes, the connected app appears under Connected Apps.
Test the sign-in
In the Web App
- In the test profile, open the Web App, then Connected Apps.
- Find the new connected app and click Authenticate.
The service provider sends you to the Web App, which opens the Log in page for the connected app. If the page asks for a value, enter it. Click Log in. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login to return to the service provider, signed in.
Only the browser profile that clicked Request Access can show Login, and only once.
The Iru web app opens, signed in as the admin user, with no Iru password prompt.
- In the test profile, open your Iru tenant’s address.
- Click Sign in with your Identity Provider, or select the
SplitSecureconnection. The service provider sends you to the Web App, which opens the Log in page for the connected app. If the page asks for a value, enter it. Click Log in. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login to return to the service provider, signed in.
Iru signs you in as the admin user.
Enforce SSO in Iru
In the Iru web app
This step is optional. Do it only after both sign-ins work.
With standard authentication disabled, no administrator can sign in to Iru with an email and password, Google or Microsoft. If you lose SSO access, only Iru Support (opens in a new tab) can turn standard authentication back on.
- In the left sidebar, click your account, then Access. Go to the Authentication methods section.
- Find the Standard Authentication connection.
- Click the ellipsis menu (⋮) and select Disable.
Troubleshooting
| Issue | Solution |
|---|---|
| The Web App refuses the Metadata Endpoint | The URL is not Iru’s service provider metadata URLPaste the exact URL from Metadata, https://<subdomain>.id.iru.com/api/v1/federated-auth/<id>/saml/metadata |
| The Web App reports no HTTP-POST ACS endpoint | Protocol Binding is HTTP-RedirectSet Protocol Binding to HTTP-Post in Iru, save, then create the connected app again |
| The Web App reports that the sign-in request is missing | Sign-In URL holds the SSO URL (HTTP-Redirect)Paste the SSO URL (HTTP-Post) in Sign-In URL |
| Iru reports that it is unable to authenticate you | Iru cannot match the userSet IdP attribute to Subject and User attribute to User Principal Name (UPN). Under Admin and authentication, make the administrator’s UPN equal the email of the person who signs in |
| Iru reports that it is unable to authenticate you after Login | The Tenant name is not the name in your Iru addressCreate the connected app again with the name in https://<name>.iru.com |
| Iru shows no SSO option on its sign-in page | The connection is disabledEnable it under your account → Access → Authentication methods |
| Nobody can sign in to Iru | Standard authentication is off and SSO failsContact Iru Support (opens in a new tab) to turn standard authentication back on |
External resources
- Single sign-on (opens in a new tab): Iru help on SSO
- SAML-based single sign-on (opens in a new tab): Iru help on custom SAML