Skip to content

Commit e33638d

Browse files
authored
Add tokens where table.
1 parent e3f29c0 commit e33638d

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

articles/active-directory/develop/authentication-scenarios.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.devlang: na
1414
ms.topic: conceptual
1515
ms.tgt_pltfrm: na
1616
ms.workload: identity
17-
ms.date: 04/05/2019
17+
ms.date: 09/23/2019
1818
ms.author: ryanwi
1919
ms.reviewer: saeeda, sureshja, hirsin
2020
ms.custom: aaddev, identityplatformtop40
@@ -57,6 +57,25 @@ In the example scenario above, you can classify the apps according to these two
5757
* Apps that need to securely access resources
5858
* Apps that play the role of the resource itself
5959

60+
### How each flow emits tokens and codes
61+
62+
Depending on how your client is built, it can use one (or several) of the authentication flows supported by the Microsoft identity platform. These flows can produce a variety of tokens (id_tokens, refresh tokens, access tokens) as well as authorization codes, and require different tokens to make them work. This chart proides an overview:
63+
64+
|Flow | Requires | id_token | access token | refresh token | authorization code |
65+
|-----|----------|----------|--------------|---------------|--------------------|
66+
|[Authorization code flow](v2-oauth2-auth-code-flow.md) | | x | x | x | x|
67+
|[Implicit flow](v2-oauth2-implicit-grant-flow.md) | | x | x | | |
68+
|[Hybrid OIDC flow](v2-protocols-oidc#get-access-tokens.md)| | x | | | | x|
69+
|[Refresh token redemption](v2-oauth2-auth-code-flow.md#refresh-the-access-token) | refresh token | x | x | x| |
70+
|[On-behalf-of flow](v2-oauth2-on-behalf-of-flow.md) | access token| x| x| x| |
71+
|[Device code flow](v2-oauth2-device-code.md) | | x| x| x| |
72+
|[Client credentials](v2-oauth2-client-creds-grant-flow.md) | | | x (app-only)| | |
73+
74+
**Notes**:
75+
76+
Tokens issued via the implicit mode have a length limitation due to being passed back to the browser via the URL (where `response_mode` is `query` or `fragment`). Some browsers have a limit on the size of the URL that can be put in the browser bar and fail when it is too long. Thus, these tokens do not have `groups` or `wids` claims.
77+
78+
6079
Now that you have an overview of the basics, read on to understand the identity app model and API, how provisioning works in Microsoft identity platform, and links to detailed info about the common scenarios that Microsoft identity platform supports.
6180

6281
## Application model

0 commit comments

Comments
 (0)