Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
For X-Broker 7.1 When submiting a SOAP request to be Identified by a WS-Security token (you previously created a Cosumer Application and a runtime policy via CentraSite Governace web interface), the SOAP-ENV:actor=“http://com.infravio.xbroker” atribute MUST be included. Otherwise X-Broker will ignore the WS-Security block.
Sample request: <soap-env:envelope xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:SOAP-ENC=“http://schemas.xmlsoap.org/soap/encoding/” xmlns:xsd=“XML Schema” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”> soap-env:header <wsse:security SOAP-ENV:actor=“http://com.infravio.xbroker” wsse:mustUnderstand=“1” xmlns:wsse=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd” xmlns:wsu=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd”> <wsse:usernametoken wsu:Id=“SecurityToken-0”> wsse:usernameca2wsuser1</wsse:Username> <wsse:password xmlns:wsse=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd” Type=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText”>manage</wsse:Password> </wsse:UsernameToken></wsse:Security></SOAP-ENV:Header>soap-env:body <tns:servicio3 xmlns:tns=“http://winxpora.webmethods.com/democap.services”> + 4 5</tns:Servicio3></SOAP-ENV:Body> </SOAP-ENV:Envelope>
Note: The value of the SOAP-ENV:actor corresponds to the one configured in the xbroker-setup.xml file (http://com.infravio.xbroker)
Suggestion: To include such a information in the product documentation