Azure AD authentication with new Microsoft Graph API (#3785)

* Azure AD authentication with new Microsoft Graph API

Added Azure AD authentication with new Microsoft Graph API

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

* Update content/chronograf/v1.9/administration/managing-security.md

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>

Co-authored-by: kelseiv <47797004+kelseiv@users.noreply.github.com>
pull/4618/head
kannapppan senthilnathan 2022-11-03 22:45:06 +01:00 committed by GitHub
parent c85cbfbc3a
commit 2365705243
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 41 additions and 1 deletions

View File

@ -362,7 +362,12 @@ export HEROKU_ORGS=hill-valley-preservation-sociey,the-pinheads
--public-url=http://<chronograf-host>:8888/
```
#### Configure Azure Active Directory authentication
#### Configure Azure Active Directory authentication with old Azure active directory Graph API
{{% warn %}}
Please note that this section is for the old Azure active directory Graph API, deprecated in June, 2022.
{{% /warn %}}
If you use the New Microsoft graph API, see how to [configure Azure Active Directory authentication with new Microsoft Graph API](#configure-azure-active-directory-authentication-with-new-microsoft-graph-api)
1. [Create an Azure Active Directory application](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application).
Note the following information: `<APPLICATION-ID>`, `<TENANT-ID>`, and `<APPLICATION-KEY>`.
@ -394,6 +399,41 @@ export HEROKU_ORGS=hill-valley-preservation-sociey,the-pinheads
Note: If youve configured TLS/SSL, modify the `PUBLIC_URL` to ensure you're using HTTPS.
#### Configure Azure Active Directory authentication with new Microsoft Graph API
1. [Create an Azure Active Directory application](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application).
Note the following information: `<APPLICATION-ID>`, `<TENANT-ID>`, and `<APPLICATION-KEY>`.
You'll need these to define your Chronograf environment.
2. Be sure to register a reply URL in your Azure application settings.
This should match the calling URL from Chronograf.
Otherwise, you will get an error stating no reply address is registered for the application.
For example, if Chronograf is configured with a `GENERIC_NAME` value of AzureAD, the reply URL would be `http://localhost:8888/oauth/AzureAD/callback`.
3. Verify that your Azure AD application has API permissions configured to sign in and read the user profile (`User.Read`) for Microsoft Graph.
4. To update the Chronograf configuration, use your Azure AD instance metadata
to set the following environment variables in `/etc/default/chronograf`:
```
GENERIC_TOKEN_URL=https://login.microsoftonline.com/<<TENANT-ID>>/oauth2/token
TENANT=<<TENANT-ID>>
GENERIC_NAME=AzureAD
GENERIC_API_KEY=userPrincipalName
GENERIC_SCOPES=openid
GENERIC_CLIENT_ID=<<APPLICATION-ID>>
GENERIC_AUTH_URL=https://login.microsoftonline.com/<<TENANT-ID>>/oauth2/authorize?resource=https://graph.microsoft.com
GENERIC_CLIENT_SECRET=<<APPLICATION-KEY>>
TOKEN_SECRET=secret
GENERIC_API_URL=https://graph.microsoft.com/v1.0/me
PUBLIC_URL=http://localhost:8888
```
{{% note %}}
**Note:** If youve configured TLS/SSL, modify the `PUBLIC_URL` to ensure you're using HTTPS.
{{% /note %}}
#### Configure Bitbucket authentication
1. Complete the instructions to [Use OAuth on Bitbucket Cloud](https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/), and include the following information: