| Summary | SOAP Fault "Access Denied" reported but no access control configured on server endpoint |
|---|---|
| Article Number | 17785 |
| Environment | All Supported Operating Systems Artix 5.1 Artix JAX-WS Runtime |
| Question/Problem Description | SOAP Fault "Access Denied" reported but no access control configured on server endpoint SOAP header UsernameToken causing the SOAP Fault "Access denied" <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>Access denied. Refer to the server log using the entry f669e274-5809-4ee7-ab1d-5b8de6c0a6d2 for details describing the reason for the failure.</faultstring> </soap:Fault> |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | A SOAP Fault stating "Access denied" is reported by Artix 5.1 JAX-WS server when a request arrives with the following SOAP header:
<soapenv:Header>
</soapenv:Header> When the password attribute is set within the UsernameToken SOAP header of the incoming request; Artix 5.1 automatically tries to endorse the credentials using com.iona.cxf.security.rt.RequireTLSCredentialEndorser. |
| Resolution | If no endorsing action is required, the following configuration will deactivate this feature: <jaxws:endpoint name="{http://apache.org/hello_world_soap_http}SoapPort">
</jaxws:endpoint> For further information please see the Artix 5.1 Security Guide, section "Artix Security Service - credentialEndorser attribute" |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#KnowledgeDocs
#Orbix