Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Procedure · 11 steps

Oracle Cloud

Sign in to the Oracle Cloud Infrastructure console through SplitSecure, so each sign-in waits for your Guardian Team to approve it.

Updated

Before you start

  • Identity Domain Administrator or Security Administrator access to an Oracle Cloud Infrastructure (OCI) tenancy with identity domains.
  • 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 Oracle Cloud a connected app of your SplitSecure identity provider, so a user signs in to the OCI console only when your Guardian Team, the group of devices that together approve each proposal, approves it. You add SplitSecure as a SAML identity provider (IdP) in an OCI identity domain, create the matching connected app, and choose whether OCI creates users at their first sign-in.

OCI signs in only a user that already exists in the identity domain, or one it creates through just-in-time (JIT) provisioning. Decide which before you create the connected app, because its fields depend on it.

Values you exchange

Value Where to find it Where to paste it
SplitSecure metadata XML The identity provider’s SAML endpoints card, Download metadata XML OCI, Import IdP metadata, in Add SplitSecure as a SAML IdP
OCI metadata XML OCI, Export SAML metadata, in Export the OCI metadata The Web App, Metadata File, in Create the connected app

Add SplitSecure as an identity provider in OCI

In the OCI console

  1. Sign in to the OCI console (opens in a new tab).
  2. Open the navigation menu and select Identity & Security.
  3. Under Identity, select Domains.
  4. Select the identity domain to configure, for example Default.
  5. Click Federation.

Download the SplitSecure metadata first.

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.

  1. Under Identity providers, click Actions → Add SAML IdP.

  2. Enter a name, for example SplitSecure, and optionally a description and a logo. Click Next.

  3. Select Import IdP metadata and upload the file from Download metadata XML. Click Next.

  4. Map the user identity, then click Next.

    Field Value
    Requested Name ID format UnspecifiedSplitSecure sends the username as the NameID
    Identity provider user attribute SAML assertion Name ID
    Identity domain user attribute Username
  5. Click Create IdP.

  1. Open the new identity provider.
  2. Click Actions → Export SAML metadata.
  3. Click Metadata File → Download XML.

Connect Oracle Cloud 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.

  1. Click the Oracle Cloud (SAML2) card.

  2. Enter a Name, for example Oracle Cloud.

  3. Keep NameID format on Unspecified and NameID value on Same for every sign-in. In NameID, enter the Username of the OCI user. Everyone who signs in through this connected app signs in as that one OCI user, so create one connected app per OCI user.

    If your OCI usernames are your members’ SplitSecure emails, select Built from each person’s email instead. One connected app then serves several people, each as their own OCI user. Create their users in OCI first, because the fields in the next step are the same for everyone.

  4. Under Metadata File, upload the XML file you exported from OCI.

  5. Set the values OCI uses to create the user through JIT provisioning. Leave them empty if the user already exists in OCI. Every sign-in through this connected app sends the same values.

    Field Value
    Email The user’s emailRequired for JIT provisioning
    First name The user’s first nameRequired for JIT provisioning
    Last name The user’s last nameRequired for JIT provisioning
    Group The name of an OCI groupOptional. It must equal the name of an existing OCI group, such as Administrators. OCI reads it only with Assign group mapping on, in Provision users below
  6. 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.

  7. 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.

Turn on the identity provider in OCI

In the OCI console

  1. Go to Federation → Identity providers.
  2. Open the SplitSecure identity provider.
  3. Click Actions → Activate IdP.

OCI shows the identity provider on its sign-in page only when a policy names it.

  1. Go to Federation → IdP policies.
  2. Open Default Identity Provider Policy, or create a policy.
  3. Click Edit IdP rule.
  4. Under Assign identity providers, add the SplitSecure identity provider.
  5. Click Save changes.

A sign-in fails when OCI finds no user with the NameID as its Username and can’t create one. Choose one option.

Just-in-time provisioning

With JIT provisioning, OCI creates the user at the first sign-in from the Email, First name, Last name and Group set on the connected app. Without Email, First name and Last name, OCI can’t create the user.

  1. Open the SplitSecure identity provider and click Actions → Configure JIT.

  2. Click Enable Just-In-Time (JIT) provisioning.

  3. Select Create a new identity domain user. Leave Update the existing identity domain user unchecked.

  4. Map the user attributes.

    IdP user attribute type IdP user attribute value Identity domain user attribute
    NameID NameID value User Name
    Attribute Email Primary Work Email
    Attribute FirstName First Name
    Attribute LastName Last name
  5. To place new users in groups, go to Map group memberships. The two options can be on together.

    • Assign domain group memberships: add the groups in the table. Every user OCI creates through SplitSecure joins them.
    • Assign group mapping: OCI reads the Group the connected app sends. Set the fields below.
    Field Value
    Group membership attribute name GroupThe attribute SplitSecure sends
    Mapping Assign implicit group membership mappingsThe connected app’s Group must equal the name of the OCI group
    When assigning group membership Merge with existing group membershipsReplace removes the user from every group the connected app doesn’t name
    When a group is not found Fail the entire requestA Group that names no OCI group then fails the sign-in
  6. Click Update.

Users created in advance

  1. Open the users page of the identity domain.

  2. Click Create user and fill in the required fields.

    Field Value
    Last name The user’s last name
    Username The connected app’s NameIDMust match exactly
    Email The user’s emailOCI can use the email as the username, or keep both
  3. Assign the user to the groups they need.

This rule is optional. It stops OCI from asking for its own second factor after a sign-in that the Guardian Team approved.

  1. Go to Domain policies → Sign-on policies.
  2. Open Security Policy for OCI Console → Sign-on rules.
  3. Click Add Sign-on rule.
  4. Name it SplitSecure IdP no MFA and select the SplitSecure identity provider in Authenticating identity provider.
  5. Leave Prompt for additional factor unchecked and click Add.
  6. Click Edit priority and move the rule to priority 1.

Test the sign-in

In the Web App

In the Web App, open Connected Apps, find the new connected app and click Log in. Some service providers, such as Iru, accept only a sign-in that starts on their side. For those, the Web App first sends you to the service provider, which sends you back. The Web App then shows the details of the connected app. If the page asks for a value, such as a NameID, enter it. To leave a note for the approvers, open Advanced Options and fill in Reason for access. Click Log in again. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login on the proposal page to finish the sign-in at the service provider.

The access form has no OCI fields. OCI receives the username and the user details set on the connected app. OCI then asks for your Cloud Account Name. Enter your tenancy name and click Next.

  1. In the test profile, open https://cloud.oracle.com/.
  2. Enter your tenancy name, click Next and select the identity domain.
  3. Click SplitSecure on the sign-in page.
  4. 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.

In a terminal

This test is optional. It needs the OCI command-line interface (CLI). To install it, follow Installing the CLI (opens in a new tab): Oracle documentation on installing the OCI CLI, or run brew install oci-cli on macOS.

  1. In a terminal, run the command below and select your region.

    Shell
    oci session authenticate
  2. In the browser window that opens, select the identity domain and click SplitSecure.

  3. 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.

  4. Return to the terminal, which confirms the session.

Troubleshooting

Issue Solution
OCI reports No user returned via correlation policy No user has the NameID as its Username, and JIT provisioning can’t create oneCreate the user in OCI, or turn on JIT provisioning and fill in Email, First name and Last name on the connected app
OCI reports that it can’t authenticate the user account, or a problem with the account you selected OCI has not applied a recent change yet, or still holds the result of a failed sign-inWait a few minutes and sign in again
OCI reports Missing required attribute(s) when you turn JIT provisioning off The OCI console sends an empty attribute mappingLeave JIT provisioning on and uncheck both Create a new identity domain user and Update the existing identity domain user
OCI rejects the SAML assertion The NameID format or attribute mapping differsSet Requested Name ID format to Unspecified and check the JIT mapping
OCI reports a certificate error The identity provider uses old metadataDownload the metadata XML again from the SAML endpoints card and import it
SplitSecure is not on the OCI sign-in page No IdP policy names the identity providerAdd it to the Default Identity Provider Policy
OCI still asks for a second factor No sign-on rule skips it for SplitSecureAdd the rule in Skip the OCI second factor at priority 1
The sign-in loops between OCI and SplitSecure Several IdP policies conflictReview the IdP policy rules and keep one that names SplitSecure

External resources