Hi,
I am using the client side authentication based on x.509 based on SSL/TLS,
whereby I am successfully authenticating the user. However, for
authorisation, on the server/resource side I have created a filter which
implements a "ContainerRequestFilter", the purpose of creating such is to
intercept the request and extract the user's x.509 in the filter method and
sending it to some external authorization framework.
Currently there is no way to achieve this except adding a "@Context
HttpServletRequest" parameter into the resource method and then reading the
x.509 from the request attributes (kind of untidy). Is there any alternative
way to get the x.509 from jersey's filtering/intercepting mechanism? or am I
missing something?
Many thanks
Sam
--
View this message in context: http://jersey.576304.n2.nabble.com/Accessing-X-509-attributes-from-filter-tp6509732p6509732.html
Sent from the Jersey mailing list archive at Nabble.com.