huwred
04/11/2024, 3:17 PMIan Robinson
04/11/2024, 5:32 PMIan Robinson
04/11/2024, 5:33 PMhuwred
04/11/2024, 5:51 PMhuwred
04/11/2024, 6:06 PMMike Chambers
04/11/2024, 9:59 PMPublicAccessChecker
https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Web.Common/Security/PublicAccessChecker.cs
Would you not have an issue though for separating out if this was the start of a new session with a successful auth ticket resolved from a cookie.. as opposed just to any request that is in due course getting a successful ticket?
Also in my limited experience, rememberme -> is persistent is only setting a 14day expiration on the cookie, it's not actually a sliding expiration (with the security ramifications of that)
I think https://docs.umbraco.com/umbraco-cms/v/12.latest/reference/configuration/securitysettings#keep-user-logged-in does actually set a sliding expiry for backoffice users though?
https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Cms.Api.Management/Configuration/ConfigureBackOfficeCookieOptions.cs#L231Mike Chambers
04/11/2024, 10:09 PMPublicAccessRequestHandler
where there is a manual call to
// manually authenticate the request
AuthenticateResult authResult =
await httpContext.AuthenticateAsync(IdentityConstants.ApplicationScheme);
https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Web.Website/Routing/PublicAccessRequestHandler.cs#L76huwred
04/12/2024, 6:44 AMMike Chambers
04/12/2024, 8:35 AMMike Chambers
04/12/2024, 8:43 AMhuwred
04/12/2024, 9:15 AMJohn Sharp
05/09/2024, 7:39 AM