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: articles/active-directory/develop/active-directory-configurable-token-lifetimes.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,11 +49,11 @@ Clients use access tokens to access a protected resource. An access token can be
49
49
50
50
### SAML tokens
51
51
52
-
SAML tokens are used by many web based SAAS applications, and are obtained using Azure Active Directory's SAML2 protocol endpoint. They are also consumed by applications using WS-Federation. The default lifetime of the token is 1 hour. After From and applications perspective the validity period of the token is specified by the NotOnOrAfter value of the <conditions …>element in the token. After the token validity period the client must initiate a new authentication request, which will often be satisfied without interactive sign in as a result of the Single Sign On (SSO) Session token.
52
+
SAML tokens are used by many web based SAAS applications, and are obtained using Azure Active Directory's SAML2 protocol endpoint. They are also consumed by applications using WS-Federation. The default lifetime of the token is 1 hour. From an application's perspective, the validity period of the token is specified by the NotOnOrAfter value of the `<conditions …>`element in the token. After the validity period of the token has ended, the client must initiate a new authentication request, which will often be satisfied without interactive sign in as a result of the Single Sign On (SSO) Session token.
53
53
54
-
The value of NotOnOrAfter can be changed using the AccessTokenLifetime parameter in a TokenLifetimePolicy. It will be set to the lifetime configured in the policy if any, plus a clock skew factor of five minutes.
54
+
The value of NotOnOrAfter can be changed using the `AccessTokenLifetime` parameter in a `TokenLifetimePolicy`. It will be set to the lifetime configured in the policy if any, plus a clock skew factor of five minutes.
55
55
56
-
Note that the subject confirmation NotOnOrAfter specified in the <SubjectConfirmationData> element is not affected by the Token Lifetime configuration.
56
+
Note that the subject confirmation NotOnOrAfter specified in the `<SubjectConfirmationData>` element is not affected by the Token Lifetime configuration.
[REST API](../../../role-based-access-control/role-assignments-rest.md), or a [Resource Manager template](../../../role-based-access-control/role-assignments-template.md).
39
+
principal. Then, grant the Azure Blueprints the _Owner_ role through the
identity](../../../active-directory/managed-identities-azure-resources/overview.md) is selected
57
-
during assignment, Blueprints creates the identity and grants the managed identity the [owner](../../../role-based-access-control/built-in-roles.md#owner)
58
-
role. If an [existing assignment is upgraded](../how-to/update-existing-assignments.md), Blueprints
59
-
uses the previously created managed identity.
68
+
during assignment, Blueprints creates the identity and grants the managed identity the
69
+
[owner](../../../role-based-access-control/built-in-roles.md#owner) role. If an
70
+
[existing assignment is upgraded](../how-to/update-existing-assignments.md), Blueprints uses the
71
+
previously created managed identity.
60
72
61
73
The managed identity related to the blueprint assignment is used to deploy or redeploy the resources
62
74
defined in the blueprint. This design avoids assignments inadvertently interfering with each other.
0 commit comments