[
https://issues.apache.org/jira/browse/KNOX-3005?focusedWorklogId=903267&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903267
]
ASF GitHub Bot logged work on KNOX-3005:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Feb/24 08:45
Start Date: 02/Feb/24 08:45
Worklog Time Spent: 10m
Work Description: smolnar82 commented on code in PR #839:
URL: https://github.com/apache/knox/pull/839#discussion_r1475738186
##########
gateway-provider-security-jwt/src/main/java/org/apache/knox/gateway/provider/federation/jwt/JWTMessages.java:
##########
@@ -104,4 +104,11 @@ public interface JWTMessages {
@Message( level = MessageLevel.WARN, text = "Invalid SSO cookie found!
Cleaning up..." )
void invalidSsoCookie();
+
+ @Message( level = MessageLevel.WARN, text = "User with SSO token {0}
exceeded the configured idle timeout of {1} seconds." )
Review Comment:
Fixed. Sample:
```
2024-02-02 09:34:59,260 24344508-5b51-4f49-8ada-87955739b8ae WARN
federation.jwt (AbstractJWTFilter.java:validateToken(354)) - User admin with
SSO token f0d51aa3...ed6d339b8f6b exceeded the configured idle timeout of 60
seconds.
2024-02-02 09:34:59,261 24344508-5b51-4f49-8ada-87955739b8ae WARN
federation.jwt (SSOCookieFederationFilter.java:handleValidationError(208)) -
Invalid SSO cookie found! Cleaning up...
```
Issue Time Tracking
-------------------
Worklog Id: (was: 903267)
Time Spent: 1h (was: 50m)
> Implement Knox idle session time
> --------------------------------
>
> Key: KNOX-3005
> URL: https://issues.apache.org/jira/browse/KNOX-3005
> Project: Apache Knox
> Issue Type: New Feature
> Components: KnoxSSO
> Affects Versions: 2.1.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Fix For: 2.1.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> With the recent work of KNOX-2961, the new SSO token invalidation
> functionality, Knox could provide idle session timeout behavior for UIs.
> It will likely not include the usual UI pop-up approach (like when the
> end-user is informed about being idle too long), but it would effectively
> terminate idle SSO sessions and force an explicit login.
> It's also worth mentioning the idleness measurement solely depends on backend
> activities through the KnoxSSO Cookie federation filter. and will not take
> any client-side action (such as scrolling on the page, client-side
> pagination, etc..) into account.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
