Skip to content

Commit e7fc92c

Browse files
authored
Merge pull request #3461 from replicatedhq/scim-draft
scim
2 parents 2a587eb + 4e4d586 commit e7fc92c

File tree

4 files changed

+371
-19
lines changed

4 files changed

+371
-19
lines changed

docs/vendor/team-management-saml-auth.md

Lines changed: 23 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,19 @@ This topic describes how to enable or disable SAML authentication for the Replic
44

55
## About Using SAML with the Vendor Portal
66

7-
After starting out with Replicated, most teams grow, adding more developers, support engineers, and sales engineers. Eventually, managing access to the Vendor Portal can become difficult. Replicated supports logging in using SAML, which lets you manage access (provisioning and unprovisioning accounts) through your SAML identity provider.
7+
After starting out with Replicated, most teams grow, adding more developers, support engineers, and sales engineers. Eventually, managing access to the Vendor Portal can become difficult. Replicated supports logging in using SAML, which lets you manage access (provisioning and deprovisioning accounts) through your SAML identity provider.
88

99
Using SAML, everyone on your team logs in with their existing usernames and passwords through your identity provider's dashboard. Users do not need to sign up through the Vendor Portal or log in with a separate Vendor Portal account, simplifying their experience.
1010

11-
### Enabling SAML in Your Vendor Account
11+
### Service Provider-Initiated Login
1212

13-
To enable SAML in your Vendor Portal account, you must have an Enterprise plan. For access to SAML, you can contact Replicated through [Support](https://vendor.replicated.com/support). For information about the Enterprise plan, see [pricing](https://www.replicated.com/pricing/).
13+
You can start the SAML sign-in flow directly from the Vendor Portal on the SAML login page at `https://vendor.replicated.com/login-saml`. Based on your team's SAML configuration, the Vendor Portal redirects you to your identity provider to complete authentication.
14+
15+
IdP-initiated login from your identity provider dashboard is also supported. By default, this only works for existing and invited users. However, your account team can optionally enable JIT provisioning of users who input email addresses that match your team's domain. This will redirect any email with `@domain.com` to your IDP for authentication.
1416

1517
### SCIM
1618

17-
Replicated does not implement System for Cross-domain Identity Management (SCIM). Instead, we use SAML to authenticate and create just-in-time user identities in our system. We resolve the username (email address) as the actor and use this to ensure that audit log events follow these dynamically provisioned users. If a user's email address is already associated with a Replicated account, by using your SAML integration to access the Vendor Portal, they automatically leave their current team and join the team associated with the SAML login.
19+
For automated user provisioning and deprovisioning, you can also enable System for Cross-domain Identity Management (SCIM). SCIM requires SAML to be configured first. For more information, see [Manage SCIM Provisioning (Beta)](team-management-scim-provisioning).
1820

1921
### Compatibility with Two-Factor Authentication
2022

@@ -24,18 +26,25 @@ If SAML authentication is configured for your team, Replicated two-factor authen
2426

2527
Replicated supports Role Based Access Control (RBAC) in the Vendor Portal. To use RBAC with SAML, you must configure policies and add users to the policies by their username. Usernames are the identity of the user in your identity provide (IDP). Typically, this username is the full email address. For more information about configuring RBAC, see [Configure RBAC Policies](team-management-rbac-configuring).
2628

27-
## Downloading Certificates from Supported SAML providers
28-
29-
You must retrieve the metadata and x.509 public certificate files from your SAML provider before configuring SAML in the Vendor Portal. The certificate file must be in PEM format.
29+
## Supported SAML Providers
3030

31-
Replicated tests several SAML providers, but the service should be compatible with any SAML 2.0 compliant service provider. We provide full support for the following SAML providers:
31+
Replicated tests several SAML providers, but the service should be compatible with any SAML 2.0 compliant service provider.
3232

33-
* Okta. For more information about integrating Okta with Replicated, see [Configure Okta](#configure-okta).
33+
Replicated provides full support for the following SAML providers:
3434

35+
* Okta
3536
* OneLogin
37+
* Duo
38+
39+
## Configure and Enable SAML
40+
41+
### Prerequisites
3642

43+
* To enable SAML in your Vendor Portal account, you must have an Enterprise plan. For access to SAML, you can contact Replicated through [Support](https://vendor.replicated.com/support). For information about the Enterprise plan, see [pricing](https://www.replicated.com/pricing/).
3744

38-
## Configure Okta
45+
* Download certificates from supported SAML providers: You must retrieve the metadata and x.509 public certificate files from your SAML provider before configuring SAML in the Vendor Portal. The certificate file must be in PEM format.
46+
47+
### Configure Okta
3948

4049
The first part of the Vendor Portal and Okta integration is configured in the Okta dashboard. This configuration lets you download the XML Metadata file and x.509 public certificate in PEM format required for the SAML authentication.
4150

@@ -69,18 +78,14 @@ To configure Okta and download the required files:
6978

7079
1. Click **Identity provider metadata** to download the Metadata.xml file. This likely opens an XML download that you can right-click and select **Save Link As…** to download this file.
7180

72-
### Next Step
81+
#### Next Step
7382

7483
Configure and enable SAML in the Vendor Portal. For more information, see [Configure SAML](#configure-saml).
7584

76-
## Configure SAML
85+
### Configure SAML
7786

7887
When you initially configure SAML, we do not recommend that you disable username/password access at the same time. It is possible, and recommended during testing, to support both SAML and non-SAML authentication on your account simultaneously.
7988

80-
**Prerequisite**
81-
82-
- Download your XML Metadata file and x.509 public certificate PEM file from your SAML provider. For more information on supported SAML providers and how to find these files, see [Supported SAML providers](#downloading-certificates-from-supported-saml-providers).
83-
8489
To configure SAML:
8590

8691
1. Log in to the Vendor Portal [Team Members page](https://vendor.replicated.com/team/members) as a user with Admin access.
@@ -96,11 +101,11 @@ To configure SAML:
96101

97102
1. Click **Upload Metadata & Cert**.
98103

99-
### Next Step
104+
#### Next Step
100105

101106
At this point, SAML is configured, but not enabled. The next step is to enable SAML enforcement options. For more information, see [Enable SAML Enforcement](#enable-saml-enforcement).
102107

103-
## Enable SAML Enforcement
108+
### Enable SAML Enforcement
104109

105110
After you have uploaded the metadata and x.509 public certificate PEM file, you must enable SAML enforcement options. Replicated provides options that can be enabled or disabled at any time. You can also change the IDP metadata if needed.
106111

0 commit comments

Comments
 (0)