Skip to content

Commit 29fbe46

Browse files
Remove disabled app reference
1 parent 7426a51 commit 29fbe46

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

articles/active-directory/develop/v2-oauth2-implicit-grant-flow.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -57,11 +57,6 @@ client_id=6731de76-14a6-49ae-97bc-6eba6914391e
5757
&nonce=678910
5858
```
5959

60-
<!--- Need to update the sample app used for testing the flow, it's disabled -->
61-
> [!TIP]
62-
> To test signing in using the implicit flow, click <a href="https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=6731de76-14a6-49ae-97bc-6eba6914391e&response_type=id_token&redirect_uri=http%3A%2F%2Flocalhost%2Fmyapp%2F&scope=openid&response_mode=fragment&state=12345&nonce=678910" target="_blank">https://login.microsoftonline.com/common/oauth2/v2.0/authorize...</a> After signing in, your browser should be redirected to `https://localhost/myapp/` with an `id_token` in the address bar.
63-
>
64-
6560
| Parameter | Type | Description |
6661
| --- | --- | --- |
6762
| `tenant` | required |The `{tenant}` value in the path of the request can be used to control who can sign into the application. The allowed values are `common`, `organizations`, `consumers`, and tenant identifiers. For more detail, see [protocol basics](active-directory-v2-protocols.md#endpoints).Critically, for guest scenarios where you sign a user from one tenant into another tenant, you *must* provide the tenant identifier to correctly sign them into the resource tenant.|

0 commit comments

Comments
 (0)