Skip to content

Commit afbc0c7

Browse files
committed
2 parents 61e754b + cd6368e commit afbc0c7

File tree

48 files changed

+1585
-971
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+1585
-971
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46580,6 +46580,11 @@
4658046580
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/overview",
4658146581
"redirect_document_id": false
4658246582
},
46583+
{
46584+
"source_path": "articles/load-balancer/load-balancer-standard-overview.md",
46585+
"redirect_url": "/azure/load-balancer/load-balancer-overview",
46586+
"redirect_document_id": false
46587+
},
4658346588
{
4658446589
"source_path": "articles/load-balancer/load-balancer-arm.md",
4658546590
"redirect_url": "/azure/load-balancer/load-balancer-overview",

articles/active-directory-b2c/active-directory-b2c-setup-goog-app.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,14 @@ ms.subservice: B2C
1818

1919
## Create a Google application
2020

21-
To use a Google account as an [identity provider](active-directory-b2c-reference-oauth-code.md) in Azure Active Directory B2C (Azure AD B2C), you need to create an application in your tenant that represents it. If you don't already have a Google account you can sign up at [https://accounts.google.com/SignUp](https://accounts.google.com/SignUp).
21+
To use a Google account as an [identity provider](active-directory-b2c-reference-oauth-code.md) in Azure Active Directory B2C (Azure AD B2C), you need to create an application in your Google Developers Console. If you don't already have a Google account you can sign up at [https://accounts.google.com/SignUp](https://accounts.google.com/SignUp).
2222

2323
1. Sign in to the [Google Developers Console](https://console.developers.google.com/) with your Google account credentials.
2424
1. In the upper-left corner of the page, select the project list, and then select **New Project**.
25-
1. Enter a **Project Name**, click **Create**, and then make sure you are using the new project.
25+
1. Enter a **Project Name**, select **Create**.
26+
1. Make sure you are using the new project by selecting the project drop-down in the top-left of the screen, select your project by name, then select **Open**.
27+
1. Select **OAuth consent screen** in the left menu, select **External**, and then select **Create**.
28+
Enter a **Name** for your application. Enter *b2clogin.com* in the **Authorized domains** section and select **Save**.
2629
1. Select **Credentials** in the left menu, and then select **Create credentials** > **Oauth client ID**.
2730
1. Under **Application type**, select **Web application**.
2831
1. Enter a **Name** for your application, enter `https://your-tenant-name.b2clogin.com` in **Authorized JavaScript origins**, and `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp` in **Authorized redirect URIs**. Replace `your-tenant-name` with the name of your tenant. You need to use all lowercase letters when entering your tenant name even if the tenant is defined with uppercase letters in Azure AD B2C.

articles/active-directory/manage-apps/application-proxy-qlik.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Follow these steps to publish your app. For a more detailed walkthrough of steps
4747
### Application #2:
4848
Follow the same steps as for Application #1, with the following exceptions:
4949

50-
**Step #5**: The Internal URL should now be the QlikSense URL with the authentication port used by the application. The default is **4244** for HTTPS, and 4248 for HTTP. Ex: **https&#58;//demo.qlik.com:4244**</br></br>
50+
**Step #5**: The Internal URL should now be the QlikSense URL with the authentication port used by the application. The default is **4244** for HTTPS, and **4248** for HTTP for QlikSense releases prior to April 2018. The default for QlikSense releases after April 2018 is **443** for HTTPS and **80** for HTTP. Ex: **https&#58;//demo.qlik.com:4244**</br></br>
5151
**Step #10:** Don’t set up SSO, and leave the **Single sign-on disabled**
5252

5353

articles/active-directory/saas-apps/awardspring-tutorial.md

Lines changed: 71 additions & 139 deletions
Large diffs are not rendered by default.
Lines changed: 147 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Fastly Edge Cloud | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and Fastly Edge Cloud.
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: dfc3c4a6-110d-4a16-b687-0fde8ac0dd53
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.topic: tutorial
16+
ms.date: 01/09/2020
17+
ms.author: jeedes
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with Fastly Edge Cloud
23+
24+
In this tutorial, you'll learn how to integrate Fastly Edge Cloud with Azure Active Directory (Azure AD). When you integrate Fastly Edge Cloud with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to Fastly Edge Cloud.
27+
* Enable your users to be automatically signed-in to Fastly Edge Cloud with their Azure AD accounts.
28+
* Manage your accounts in one central location - the Azure portal.
29+
30+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
31+
32+
## Prerequisites
33+
34+
To get started, you need the following items:
35+
36+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37+
* Fastly Edge Cloud single sign-on (SSO) enabled subscription.
38+
39+
## Scenario description
40+
41+
In this tutorial, you configure and test Azure AD SSO in a test environment.
42+
43+
* Fastly Edge Cloud supports **IDP** initiated SSO
44+
45+
## Adding Fastly Edge Cloud from the gallery
46+
47+
To configure the integration of Fastly Edge Cloud into Azure AD, you need to add Fastly Edge Cloud from the gallery to your list of managed SaaS apps.
48+
49+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
50+
1. On the left navigation pane, select the **Azure Active Directory** service.
51+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
52+
1. To add new application, select **New application**.
53+
1. In the **Add from the gallery** section, type **Fastly Edge Cloud** in the search box.
54+
1. Select **Fastly Edge Cloud** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
55+
56+
## Configure and test Azure AD single sign-on for Fastly Edge Cloud
57+
58+
Configure and test Azure AD SSO with Fastly Edge Cloud using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Fastly Edge Cloud.
59+
60+
To configure and test Azure AD SSO with Fastly Edge Cloud, complete the following building blocks:
61+
62+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
63+
* **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
64+
* **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
65+
1. **[Configure Fastly Edge Cloud SSO](#configure-fastly-edge-cloud-sso)** - to configure the single sign-on settings on application side.
66+
* **[Create Fastly Edge Cloud test user](#create-fastly-edge-cloud-test-user)** - to have a counterpart of B.Simon in Fastly Edge Cloud that is linked to the Azure AD representation of user.
67+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
68+
69+
## Configure Azure AD SSO
70+
71+
Follow these steps to enable Azure AD SSO in the Azure portal.
72+
73+
1. In the [Azure portal](https://portal.azure.com/), on the **Fastly Edge Cloud** application integration page, find the **Manage** section and select **single sign-on**.
74+
1. On the **Select a single sign-on method** page, select **SAML**.
75+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
76+
77+
![Edit Basic SAML Configuration](common/edit-urls.png)
78+
79+
1. On the **Basic SAML Configuration** section, enter the values for the following fields:
80+
81+
In the **Identifier** text box, type a URL using the following pattern:
82+
`https://api.fastly.com/saml/<CUSTOM_IDENTIFIER>`
83+
84+
> [!NOTE]
85+
> This value is not real. Update the value with the actual Identifier. Contact [Fastly Edge Cloud Client support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
86+
87+
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
88+
89+
![The Certificate download link](common/metadataxml.png)
90+
91+
1. On the **Set up Fastly Edge Cloud** section, copy the appropriate URL(s) based on your requirement.
92+
93+
![Copy configuration URLs](common/copy-configuration-urls.png)
94+
95+
### Create an Azure AD test user
96+
97+
In this section, you'll create a test user in the Azure portal called B.Simon.
98+
99+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
100+
1. Select **New user** at the top of the screen.
101+
1. In the **User** properties, follow these steps:
102+
1. In the **Name** field, enter `B.Simon`.
103+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
104+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
105+
1. Click **Create**.
106+
107+
### Assign the Azure AD test user
108+
109+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Fastly Edge Cloud.
110+
111+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
112+
1. In the applications list, select **Fastly Edge Cloud**.
113+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
114+
115+
![The "Users and groups" link](common/users-groups-blade.png)
116+
117+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
118+
119+
![The Add User link](common/add-assign-user.png)
120+
121+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
122+
1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
123+
1. In the **Add Assignment** dialog, click the **Assign** button.
124+
125+
## Configure Fastly Edge Cloud SSO
126+
127+
To configure single sign-on on **Fastly Edge Cloud** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Fastly Edge Cloud support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
128+
129+
### Create Fastly Edge Cloud test user
130+
131+
In this section, you create a user called B.Simon in Fastly Edge Cloud. Work with [Fastly Edge Cloud support team](mailto:[email protected]) to add the users in the Fastly Edge Cloud platform. Users must be created and activated before you use single sign-on.
132+
133+
## Test SSO
134+
135+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
136+
137+
When you click the Fastly Edge Cloud tile in the Access Panel, you should be automatically signed in to the Fastly Edge Cloud for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
138+
139+
## Additional resources
140+
141+
- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
142+
143+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
144+
145+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
146+
147+
- [Try Fastly Edge Cloud with Azure AD](https://aad.portal.azure.com/)

0 commit comments

Comments
 (0)