Skip to content

Commit 305d658

Browse files
author
AmanpreetSingh-MSFT
authored
(AzureCXP) fixes MicrosoftDocs/azure-docs#88231
Updated line no. 209. Current version: We recommend that you set the value of SessionExpiryInSeconds to be a short period (1200 seconds), while the value of KeepAliveInDays can be set to a relatively long period (30 days), as shown in the following example: New version: We set both KeepAliveInDays and SessionExpiryInSeconds so that during a sign-in if a user selects the KMSI checkbox, the KeepAliveInDays is used otherwise the value specified in the SessionExpiryInSeconds parameter is used to set the cookies. We recommend that you set the value of SessionExpiryInSeconds to be a short period (1200 seconds), while the value of KeepAliveInDays can be set to a relatively long period (30 days), as shown in the following example:
1 parent cd4da46 commit 305d658

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory-b2c/session-behavior.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ Update the relying party (RP) file that initiates the user journey that you crea
206206
</UserJourneyBehaviors>
207207
```
208208

209-
We recommend that you set the value of SessionExpiryInSeconds to be a short period (1200 seconds), while the value of KeepAliveInDays can be set to a relatively long period (30 days), as shown in the following example:
209+
We set both KeepAliveInDays and SessionExpiryInSeconds so that during a sign-in if a user selects the KMSI checkbox, the KeepAliveInDays is used otherwise the value specified in the SessionExpiryInSeconds parameter is used to set the cookies. We recommend that you set the value of SessionExpiryInSeconds to be a short period (1200 seconds), while the value of KeepAliveInDays can be set to a relatively long period (30 days), as shown in the following example:
210210

211211
```xml
212212
<RelyingParty>

0 commit comments

Comments
 (0)