mod_osso headers missing on successful authentication
What would cause mod_osso headers to be missing on a successful authentication?
I've checked the OSSO configuration file to make sure things such as encryption keys and site IDs are correct.
I am using dynamic directives.
I have the OHS configured in a reverse proxy setup; it is currently proxying to a Python script that simply sends 499 if the "Osso-User-Guid" header is missing, and 200 with message "Ok" if it is present. I am 100% certain that the script isn't modifying the incoming headers. I used "ngrep" to see what packets the OHS is receiving from Oracle's SSO instance and none of the relevant authentication headers are present (at least in plaint text). What I do see is the server receiving something like "/osso_login_success?urlc=v1.4%<very long string of hex characters>" followed by standard/normal HTTP headers.
I've checked the OSSO configuration file to make sure things such as encryption keys and site IDs are correct.
I am using dynamic directives.
I have the OHS configured in a reverse proxy setup; it is currently proxying to a Python script that simply sends 499 if the "Osso-User-Guid" header is missing, and 200 with message "Ok" if it is present. I am 100% certain that the script isn't modifying the incoming headers. I used "ngrep" to see what packets the OHS is receiving from Oracle's SSO instance and none of the relevant authentication headers are present (at least in plaint text). What I do see is the server receiving something like "/osso_login_success?urlc=v1.4%<very long string of hex characters>" followed by standard/normal HTTP headers.
0