>>>>> Jean-Baptiste Onofré <[email protected]>:
> AFAIK, it's not yet possible, but it makes sense to have something
> configurable there.
Ok, that means I'll have to resort to plan B, and it isn't pretty...:-)
1. Add another jersey endpoint
2. in that endpoint inject the jsessionid cookie
3. 302 to the jersey endpoint after a successful auth
4. in the jersey endpoint set the jsessionid cookie under a new path
and then redirect to the original URL
(It's a hack and I was hoping there was a simple way to avoid it...)
