A customer is attempting to integrate HCL Verse with an Apache Reverse Proxy and requires greater visibility into the authentication process and cookie handling mechanisms used during user login.
Currently, administrators have limited ability to determine:
Which login forms are invoked during the Verse authentication process.
Whether custom cookie-generation formulas are executed successfully.
How authentication requests are processed when a reverse proxy is used.
How server affinity and routing cookies are generated and consumed by Verse and Domino.
Why expected cookie values may not be populated during login.
The customer would like the product to provide improved diagnostic capabilities, logging, or administrative visibility that would allow administrators to trace the authentication flow and validate cookie generation when deploying Verse behind a reverse proxy.
Requested Enhancement:
Provide functionality that enables administrators to:
Trace the authentication workflow used by Verse.
Identify the forms and events involved during the login process.
Verify execution of custom authentication and cookie-generation logic.
Monitor cookie creation and value assignment during user authentication.
Obtain detailed diagnostic information to assist with reverse proxy integrations and troubleshooting.
You can use the browser's debug tools to see which cookies will get issue to the client.
Which login forms are used are defined in the domcfg.nsf database.
To troubleshoot authentication issues, debug parameters can be set on the server.
However, we have no plans to expose how session cookies are computed.
What I dont quite understand is the actual problem that you are trying to solve. Are you having problems configuring Verse behind a Proxy ?