Update AzureAD setup instructions
@@ -28,9 +28,8 @@ Configuring Rancher to allow your users to authenticate with their Azure AD acco
|
||||
- [1. Register Rancher with Azure](#1-register-rancher-with-azure)
|
||||
- [2. Create an Azure API Key](#2-create-an-azure-api-key)
|
||||
- [3. Set Required Permissions for Rancher](#3-set-required-permissions-for-rancher)
|
||||
- [4. Add a Reply URL](#4-add-a-reply-url)
|
||||
- [5. Copy Azure Application Data](#5-copy-azure-application-data)
|
||||
- [6. Configure Azure AD in Rancher](#6-configure-azure-ad-in-rancher)
|
||||
- [4. Copy Azure Application Data](#4-copy-azure-application-data)
|
||||
- [5. Configure Azure AD in Rancher](#5-configure-azure-ad-in-rancher)
|
||||
|
||||
<!-- /TOC -->
|
||||
|
||||
@@ -44,39 +43,43 @@ Before enabling Azure AD within Rancher, you must register Rancher with Azure.
|
||||
|
||||

|
||||
|
||||
1. Click **New application registration** and complete the **Create** form.
|
||||
1. Click **New registrations** and complete the **Create** form.
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||
|
||||
1. Enter a **Name** (something like `Rancher`).
|
||||
|
||||
1. From **Application type**, make sure that **Web app / API** is selected.
|
||||
1. From **Supported account types**, select "Accounts in this organizational directory only (AzureADTest only - Single tenant)" This corresponds to the legacy app registration options.
|
||||
|
||||
1. In the **Sign-on URL** field, enter the URL of your Rancher Server.
|
||||
1. In the **Redirect URI** section, make sure **Web** is selected from the dropdown and enter the URL of your Rancher Server in the text box next to the dropdown. This Rancher server URL should be appended with the verification path: `<MY_RANCHER_URL>/verify-auth-azure`.
|
||||
|
||||
1. Click **Create**.
|
||||
>**Tip:** You can find your personalized Azure reply URL in Rancher on the Azure AD Authentication page (Global View > Security Authentication > Azure AD).
|
||||
|
||||
### 2. Create an Azure API Key
|
||||
1. Click **Register**.
|
||||
|
||||
From the Azure portal, create an API key. Rancher will use this key to authenticate with Azure AD.
|
||||
>**Note:** It can take up to five minutes for this change to take affect, so don't be alarmed if you can't authenticate immediately after Azure AD configuration.
|
||||
|
||||
### 2. Create a new client secret
|
||||
|
||||
From the Azure portal, create a client secret. Rancher will use this key to authenticate with Azure AD.
|
||||
|
||||
1. Use search to open **App registrations** services. Then open the entry for Rancher that you created in the last procedure.
|
||||
|
||||

|
||||
|
||||
**Step Result:** A new blade opens for Rancher.
|
||||
1. From the navigation pane on left, click **Certificates and Secrets**.
|
||||
|
||||
1. Click **Settings**.
|
||||
1. Click **New client secret**.
|
||||
|
||||
1. From the **Settings** blade, select **Keys**.
|
||||

|
||||
|
||||
1. From **Passwords**, create an API key.
|
||||
1. Enter a **Description** (something like `Rancher`).
|
||||
|
||||
1. Enter a **Key description** (something like `Rancher`).
|
||||
1. Select duration for the key from the options under **Expires**. This drop-down sets the expiration date for the key. Shorter durations are more secure, but require you to create a new key after expiration.
|
||||
|
||||
1. Select a **Duration** for the key. This drop-down sets the expiration date for the key. Shorter durations are more secure, but require you to create a new key after expiration.
|
||||
|
||||
1. Click **Save** (you don't need to enter a value—it will automatically populate after you save).
|
||||
1. Click **Add** (you don't need to enter a value—it will automatically populate after you save).
|
||||
<a id="secret"></a>
|
||||
|
||||
1. Copy the key value and save it to an [empty text file](#tip).
|
||||
@@ -89,13 +92,16 @@ From the Azure portal, create an API key. Rancher will use this key to authentic
|
||||
|
||||
Next, set API permissions for Rancher within Azure.
|
||||
|
||||
1. From the **Settings** blade, select **Required permissions**.
|
||||
1. From the navigation pane on left, select **API permissions**.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Click **Windows Azure Active Directory**.
|
||||
1. Click **Add a permission**.
|
||||
|
||||
1. From the **Azure Active Directory Graph**, select the following **Delegated Permissions**:
|
||||
|
||||

|
||||
|
||||
1. From the **Enable Access** blade, select the following **Delegated Permissions**:
|
||||
<br/>
|
||||
<br/>
|
||||
- **Access the directory as the signed-in user**
|
||||
@@ -105,43 +111,21 @@ Next, set API permissions for Rancher within Azure.
|
||||
- **Read all users' basic profiles**
|
||||
- **Sign in and read user profile**
|
||||
|
||||
1. Click **Save**.
|
||||
1. Click **Add permissions**.
|
||||
|
||||
1. From **Required permissions**, click **Grant permissions**. Then click **Yes**.
|
||||
1. From **API permissions**, click **Grant admin consent**. Then click **Yes**.
|
||||
|
||||
>**Note:** You must be signed in as an Azure administrator to successfully save your permission settings.
|
||||
|
||||
|
||||
### 4. Add a Reply URL
|
||||
|
||||
To use Azure AD with Rancher you must whitelist Rancher with Azure. You can complete this whitelisting by providing Azure with a reply URL for Rancher, which is your Rancher Server URL followed with a verification path.
|
||||
|
||||
|
||||
1. From the **Setting** blade, select **Reply URLs**.
|
||||
|
||||

|
||||
|
||||
1. From the **Reply URLs** blade, enter the URL of your Rancher Server, appended with the verification path: `<MY_RANCHER_URL>/verify-auth-azure`.
|
||||
|
||||
>**Tip:** You can find your personalized Azure reply URL in Rancher on the Azure AD Authentication page (Global View > Security Authentication > Azure AD).
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
**Result:** Your reply URL is saved.
|
||||
|
||||
>**Note:** It can take up to five minutes for this change to take affect, so don't be alarmed if you can't authenticate immediately after Azure AD configuration.
|
||||
|
||||
### 5. Copy Azure Application Data
|
||||
### 4. Copy Azure Application Data
|
||||
|
||||
As your final step in Azure, copy the data that you'll use to configure Rancher for Azure AD authentication and paste it into an empty text file.
|
||||
|
||||
1. Obtain your Rancher **Tenant ID**.
|
||||
|
||||
1. Use search to open the **Azure Active Directory** service.
|
||||
1. From **App registrations** select the app configured above.
|
||||
|
||||

|
||||
|
||||
1. From the **Azure Active Directory** menu, open **Properties**.
|
||||
1. From the left navigation pane, open **Overview**.
|
||||
|
||||
2. Copy the **Directory ID** and paste it into your [text file](#tip).
|
||||
|
||||
@@ -171,7 +155,7 @@ As your final step in Azure, copy the data that you'll use to configure Rancher
|
||||
|
||||
>**Note:** Copy the v1 version of the endpoints
|
||||
|
||||
### 6. Configure Azure AD in Rancher
|
||||
### 5. Configure Azure AD in Rancher
|
||||
|
||||
From the Rancher UI, enter information about your AD instance hosted in Azure to complete configuration.
|
||||
|
||||
|
||||
|
After Width: | Height: | Size: 116 KiB |
|
After Width: | Height: | Size: 222 KiB |
|
After Width: | Height: | Size: 292 KiB |
|
After Width: | Height: | Size: 41 KiB |
|
After Width: | Height: | Size: 252 KiB |
|
After Width: | Height: | Size: 219 KiB |
|
After Width: | Height: | Size: 390 KiB |