Red Hat Bugzilla – Bug 780058
SOAPProxy does not support access of unauthenticated clients to authenticated proxied service
Last modified: 2011-02-15 03:29:19 EST
If there are static authentication information stored for SOAPProxy like
and the SOAPProxy service contains configuration option
<property name="clientCredentialsRequired" value="false" />
Then the client should be able to invoke the service without authentication but now
HTTP/1.1 401 Unauthorized[\r][\n]
This scenario worked for 5.0.2
Attachment: Added: wsp.zip
Link: Added: This issue depends JBESB-3519
It is not SOAPProxy but, rather, the http gateway which is restricting access.
Writer: Added: Darrin
Release Notes Docs Status: Added: Not Yet Documented
Verified in ER6
Reopening to add release note information. Will set back to Closed -> Done shortly.
Setting back to Closed -> Done after adding release note details.
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: If authentication information was stored for SOAPProxy, clients without authentication information could not invoke the service, even when the clientCredentialsRequired property was set to false. Authentication is no longer required when this property is false, even if authentication information is stored.