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
Which version of Duende IdentityServer are you using?
7.0.8
Which version of .NET are you using?
8.0
Describe the issue
I have two hosts running on two different domains. One host authenticates users for the other external one. The authentication process works perfectly.
What I need to be done next is to increase the lifetime of the issued cookie for the external host. I have already customized the authentication host cookie lifetime(MaxAge) using ConfigureApplicationCookie. On every new session, the external host always redirects user to get authenticated. Because the user is already logged in the main authentication domain (the user already has an identity cookie) the user gets instantly redirected to the external domain authenticated, until the session is ended.
What has been tried?
AddIdentityServer cookie settings
Configure one host to authenticate users for the other using Duende.IdentityServer 7.0.8.
Customize the authentication cookie settings using AddIdentityServer and set options.Authentication.CookieLifetime.
Authenticate a user and check the cookie settings in the browser.
Result
This breaks authentication in the main host without even solving the problem. The authentication cookie gets cleared instantly after logging into the main host.
ConfigureExternalCookie cookie settings
Same as previous but this time using options.ExpireTimeSpan of ConfigureExternalCookie.
Authenticate a user and check the cookie settings in the browser.
Result
No change in behaviour.
Expected behavior
The customized authentication cookie settings, such as CookieLifetime, should be applied to the cookie issued to the user's browser in the external host.
The text was updated successfully, but these errors were encountered:
You have two identity provider applications on separate hosts, both running IdentityServer
No. Two separate hosts on two different domains. one identity provider (which have its own front-end including login forms, profile management, etc.). The other one is a mere front-end which requires authorized access and is a client for the identity provider (I called this one 'the external one').
One is configured as an external identity provider for the other
yes.
You want to extend the session cookie lifetime for the external one
I want to extend the lifetime of the cookies issued to the client users. The lifetime of the cookies issued to the identity provider host users itself are correctly customized.
Sorry for ambiguity in the problem statement. And thank you for your help.
Which version of Duende IdentityServer are you using?
7.0.8
Which version of .NET are you using?
8.0
Describe the issue
I have two hosts running on two different domains. One host authenticates users for the other external one. The authentication process works perfectly.
What I need to be done next is to increase the lifetime of the issued cookie for the external host. I have already customized the authentication host cookie lifetime(MaxAge) using
ConfigureApplicationCookie
. On every new session, the external host always redirects user to get authenticated. Because the user is already logged in the main authentication domain (the user already has an identity cookie) the user gets instantly redirected to the external domain authenticated, until the session is ended.What has been tried?
AddIdentityServer
cookie settingsDuende.IdentityServer 7.0.8
.AddIdentityServer
and setoptions.Authentication.CookieLifetime
.Result
This breaks authentication in the main host without even solving the problem. The authentication cookie gets cleared instantly after logging into the main host.
ConfigureExternalCookie
cookie settingsoptions.ExpireTimeSpan
ofConfigureExternalCookie
.Result
No change in behaviour.
Expected behavior
The customized authentication cookie settings, such as
CookieLifetime
, should be applied to the cookie issued to the user's browser in the external host.The text was updated successfully, but these errors were encountered: