In xDM v5.3, Why Is Current Username No Longer Added to Tomcat Access Logs?
In 5.3 the authentication is not handled by tomcat anymore and so the %u does not return the username anymore.
However, xDM adds the username as a session attribute so if you add {userName}s to the Access Log Valve pattern, it should log the username.
Stéphanie FOURRIER
In xDM v5.3, Why Is Current Username No Longer Added to Tomcat Access Logs?
In 5.3 the authentication is not handled by tomcat anymore and so the %u does not return the username anymore.
However, xDM adds the username as a session attribute so if you add {userName}s to the Access Log Valve pattern, it should log the username.
Stéphanie FOURRIER
In 5.3 the authentication is not handled by tomcat anymore and so the %u does not return the username anymore.
However, xDM adds the username as a session attribute so if you add {userName}s to the Access Log Valve pattern, it should log the username.
-
Deployment History Date
-
Is It Possible to Perform Automatic Authentication with The User's Windows Account?
-
Where is the documentation for Version 5.2.5?
-
On Prem Semarchy Authentication using Azure AD?
-
Delete old models
-
Sync production model version with dev
-
Recreate a dev environment. Any side effect?
-
Indexes on xDM database tables
-
What logging technology is used in the Semarchy xDM platform?
See all 64 topics