diff --git a/website/docs/advanced/code-references/bitbucket-pipe.mdx b/website/docs/advanced/code-references/bitbucket-pipe.mdx index b5d380ab..228980aa 100644 --- a/website/docs/advanced/code-references/bitbucket-pipe.mdx +++ b/website/docs/advanced/code-references/bitbucket-pipe.mdx @@ -10,7 +10,7 @@ You can find more information about Bitbucket Pipelines ConfigCat Management API credential and store its values in secure pipeline variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - Bitbucket Pipe secrets + Bitbucket Pipe secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/advanced/code-references/bitrise-step.mdx b/website/docs/advanced/code-references/bitrise-step.mdx index a78685d1..b79bb990 100644 --- a/website/docs/advanced/code-references/bitrise-step.mdx +++ b/website/docs/advanced/code-references/bitrise-step.mdx @@ -10,7 +10,7 @@ to automatically scan your source code for feature flag and setting usages and u ## Setup 1. Create a new ConfigCat Management API credential and store its values in secure pipeline variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - Bitrise secrets + Bitrise secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/advanced/code-references/circleci-orb.mdx b/website/docs/advanced/code-references/circleci-orb.mdx index 3acd041a..bec284a3 100644 --- a/website/docs/advanced/code-references/circleci-orb.mdx +++ b/website/docs/advanced/code-references/circleci-orb.mdx @@ -10,7 +10,7 @@ You can find more information about CircleCI Orbs ConfigCat Management API credential and store its values in CircleCI Environment Variables with the following names: `CONFIGCAT_API_USER`, `CONFIGCAT_API_PASS`. - CircleCI Orb secrets + CircleCI Orb secrets 2. Get your selected [Config's ID](overview.mdx#config-id). diff --git a/website/docs/advanced/team-management/auto-assign-users.mdx b/website/docs/advanced/team-management/auto-assign-users.mdx index 7a801936..974e94b5 100644 --- a/website/docs/advanced/team-management/auto-assign-users.mdx +++ b/website/docs/advanced/team-management/auto-assign-users.mdx @@ -11,14 +11,14 @@ Furthermore, you can also set which Organization roles / Product permissions the - Open your organization's authentication settings on the ConfigCat Dashboard. - Authentication settings + Authentication settings - Select the domain you want to configure, and click `RE-CONFIGURE` (or just `CONFIGURE` if you haven’t configured it yet) under the `Auto-assign status`. - Auto-assign configuration + Auto-assign configuration - In the dialog that appears, you can select which `Organization roles` and `Product permissions` should be assigned to the newly registered users. - Auto-assign setup + Auto-assign setup - When you are ready, just hit `Save`. diff --git a/website/docs/advanced/team-management/domain-verification.mdx b/website/docs/advanced/team-management/domain-verification.mdx index 214bded3..928fbe82 100644 --- a/website/docs/advanced/team-management/domain-verification.mdx +++ b/website/docs/advanced/team-management/domain-verification.mdx @@ -10,16 +10,16 @@ In order to use the [SAML Single Sign-On](../../advanced/team-management/saml/ov - Open your organization's authentication settings on the ConfigCat Dashboard. - ConfigCat authentication settings + ConfigCat authentication settings - Click `ADD & VERIFY DOMAIN`. - ConfigCat add & verify domain + ConfigCat add & verify domain - Type your domain name, then click `ADD` - ConfigCat add domain + ConfigCat add domain - Follow the instructions on the appearing dialog to verify your domain. - ConfigCat verify domain + ConfigCat verify domain diff --git a/website/docs/advanced/team-management/saml/identity-providers/adfs.mdx b/website/docs/advanced/team-management/saml/identity-providers/adfs.mdx index b3c0c7ba..2b39cfc6 100644 --- a/website/docs/advanced/team-management/saml/identity-providers/adfs.mdx +++ b/website/docs/advanced/team-management/saml/identity-providers/adfs.mdx @@ -17,77 +17,77 @@ Each SSO Identity Provider requires specific information to configure a SAML int - Open your organization's authentication settings on the ConfigCat Dashboard. - ConfigCat authentication settings + ConfigCat authentication settings - Click `ADD SAML IDENTITY PROVIDER`. - ConfigCat Add Identity Provider + ConfigCat Add Identity Provider - Give a name for your Identity Provider, and click `Create`. - ConfigCat Name Identity Provider + ConfigCat Name Identity Provider - From the next section of the dialog, copy the following values and save them for further use. - `Entity ID` - `Assertion Consumer Service` - ConfigCat SAML configuration + ConfigCat SAML configuration ## 2. Configure a Relying Party Trust - Open the ADFS Management console, and click `Add Relying Party Trust`. - ADFS add relying party trust + ADFS add relying party trust - Make sure the `Claims aware` option is selected, and click `Start`. - ADFS claims aware + ADFS claims aware - Select the `Enter data about this relying party manually` option, and click `Next`. - ADFS manual relying party setup + ADFS manual relying party setup - Type a descriptive `Display name`, and click `Next`. - ADFS display name + ADFS display name - No action required on the `Configure Certificate` pane, click `Next`. - ADFS certificate configuration + ADFS certificate configuration - Select the `Enable support for the SAML 2.0 WebSSO protocol` option, and paste the value of `Assertion Consumer Service` from [Step 1](#1-collect-saml-metadata-from-configcat) into the `Relying party SAML 2.0 SSO service URL` field. Then, Click `Next`. - ADFS acs URL + ADFS acs URL - Paste the value of `Entity ID` from [Step 1](#1-collect-saml-metadata-from-configcat) into the `Relying party trust identifier` field, and click `Add`. Then, click `Next`. - ADFS entity ID + ADFS entity ID - No action required on the `Choose Access Control Policy` pane, click `Next`. - ADFS Access Control Policy + ADFS Access Control Policy - Review the changes, then click `Next`. - ADFS add trust + ADFS add trust - The Relying Party Trust is now successfully added, make sure the `Configure claims issuance policy for this application` option is checked, and click `Close`. - ADFS finish configuration + ADFS finish configuration ## 3. Configure Claims Issuance Policy - After adding the Relying Party Trust, the following dialog should appear. Click `Add rule`. - ADFS edit claims + ADFS edit claims - Select `Send LDAP Attributes as Claims` as the `Claim rule template`, and click `Next`. - ADFS LDAP claims + ADFS LDAP claims - Apply the following, and click `Finish`. @@ -96,11 +96,11 @@ Click `Add rule`. - Select `User-Principal-Name` as `LDAP Attribute`. - Select `Name ID` as `Outgoing Claim Type`. - ADFS unc to nameid + ADFS unc to nameid - Click `OK`. - ADFS finish claims + ADFS finish claims ## 4. Configure ConfigCat with SAML Details from ADFS @@ -111,15 +111,15 @@ You can choose one of the following options to configure ConfigCat with SAML Ide