You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/spring/azure-spring-boot-starter-active-directory-b2c/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ accept or deny access after validating access_token obtained from Azure AD. We w
49
49
1. Accessing a resource server.
50
50
1. Resource server accessing other resource servers.
51
51
52
-

52
+

53
53
54
54
### Accessing a web application
55
55
@@ -71,7 +71,7 @@ This scenario uses the [The OAuth 2.0 authorization code grant] flow to login in
71
71
select **Delegated permissions**, check **offline_access** and **openid** permissions, select **Add permission** to complete the process.
72
72
73
73
1. Grant admin consent for ***Graph*** permissions.
Copy file name to clipboardExpand all lines: sdk/spring/azure-spring-boot-starter-active-directory/README.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,14 +31,14 @@ This scenario uses the [The OAuth 2.0 authorization code grant] flow to login in
31
31
32
32
**System diagram**:
33
33
34
-

34
+

35
35
36
36
37
37
* Step 1: Make sure `redirect URI` has been set to `{application-base-uri}/login/oauth2/code/`, for
38
38
example `http://localhost:8080/login/oauth2/code/`. Note the tailing `/` cannot be omitted.
* Step 1: Make sure `redirect URI` has been set, just like [Accessing a web application].
102
102
@@ -150,7 +150,7 @@ This scenario not support login. Just protect the server by validating the acces
150
150
151
151
**System diagram**:
152
152
153
-

153
+

154
154
155
155
To use **aad-starter** in this scenario, we need these steps:
156
156
@@ -179,8 +179,8 @@ To use **aad-starter** in this scenario, we need these steps:
179
179
```
180
180
Both `client-id` and `app-id-uri` can be used to verify access token. `app-id-uri` can be get in Azure Portal:
To use **aad-starter** in this scenario, we need these steps:
218
218
@@ -480,7 +480,7 @@ This starter supports [Conditional Access] policy. By using [Conditional Access]
480
480
481
481
In [Resource server visiting other resource server] scenario(For better description, we think that resource server with OBO function as **webapiA** and the other resource servers as **webapiB**), When we configure the webapiB application with Conditional Access(such as [multi-factor authentication]), this stater will help us send the Conditional Access information of the webapiA to the web application and the web application will help us complete the Conditional Access Policy. As shown below:

37
+

38
38
39
39
1. On the **Create key vault** page, input `Subscription`, `Resource group`, `Key vault name` and `Pricing tier`, then click `Review + Create`.
40
40
41
-

41
+


48
48
49
49
1. When the page for your app registration appears, copy your **Vault URI**;
1. After the certificate is successfully created, it takes a while for the status to become `Enabled`. You can click **refresh** to check current status.
This starter allows you to securely manage and tightly control your certificates by using Azure Key Vault or side-load certificates by supplying them as part of the application.
@@ -74,31 +74,31 @@ This starter allows you to securely manage and tightly control your certificates
74
74
75
75
2. Click **Azure Active Directory**.
76
76
77
-

77
+

78
78
79
79
1. From the portal menu, Click **App registrations**,
1. When the page for your app registration appears, copy your **Application ID** and the **Tenant ID**;
90
90
91
-

91
+

92
92
93
93
1. Click **Certificates & secrets** in the left navigation pane. Then click **New client secret**.
94
94
95
95
1. Add a **Description** and click duration in the **Expires** list. Click **Add**. The value for the key will be automatically filled in.
@@ -119,23 +119,23 @@ Make sure the client-id can access target Key Vault. Here are steps to configure
119
119
120
120
1. Type your key vault name in **Search resources, services, and docs** and click your key vault created before.
121
121
122
-

122
+

123
123
124
124
1. Click **Access policies** in the left navigation pane. Then click **Add Access Policy**.
0 commit comments