Does anyone know if xdmp:get-request-username() is guaranteed to always return 
the username of the Authorization header for a request even when that 
Authorization header is not specific to Mark Logic? For example, when 
application-level authentication is configured for an http app server but Mark 
Logic is sitting behind apache acting as a reverse proxy that required basic 
auth to get to the applications behind apache I'm letting that header through 
and the Mark Logic application is decoding it and returning the username for 
the xdmp:get-request-username() call even though Mark Logic isn't protecting 
via basic auth. Is that always guaranteed to work? The 3.2. documentation for 
that method does not make it clear from where it gets its information for the 
request.

Mark

----------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message.
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to