Ahh .. that makes sense. If I may make one suggestion though -- you can use
CASAuthNHeader with a more descriptive name. For example:
CASAuthNHeader USER_NAME
And then, you can use request.getHeader("USER_NAME").
HTH,
-Matt
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Srikar Kummamuri
Sent: Thu 2008-01-10 18:22
To: Srikar Kummamuri; [email protected]
Subject: RE: mod_auth_cas-1.0.6 released
Matt,
In one application out of many, MicroStrategy (Business Intelligence
Server) on which I am working is not exposing the http request API, so
that I get the user form the request directly. They exposed a very
little code in their SDK and abstracted the http request object. I am
dealing with them to see on getting the remote user. But their API is
exposing the method to get the header value. So in other words, I can
not call request.gerRemoteUser() in the code they exposed, but I can
call request.getHeader.
So that is the reason why I will be using both, request.getRemoteUser in
other apps and request.getHeader("on") in the MicroStretagy SDK.
Thanks for the help.
Srikar.
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
