Hello -- Is there a way to allow an unauthenticated POST request from a non-interactive client using X509 certificates for authentication to remain a POST request once it authenticates properly? The 302 redirects of the request as a function of authentication cause the original request to end up a GET on the resource.
I'm using a Jersey client implementation to initiate the request and have configured it to follow redirects automatically. The authentication succeeds. It all looks fine, with the exception of the change in the method. I'd be very interested in hearing how others have addressed this issue, or what I might be able to do in order to surmount this problem. All suggestions welcome. Thank you for reading. I look forward to your replies. Peace. -- View this message in context: http://jasig.275507.n4.nabble.com/X509-authentication-POST-request-to-resource-turns-the-request-into-a-GET-tp4656744.html Sent from the CAS Developers mailing list archive at Nabble.com. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
