[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (WSBRSP-4) Kerberos token message BSP3032 assertion failure with correct ValueType
Kerberos token message BSP3032 assertion failure with correct ValueType ------------------------------------------------------------------------ Key: WSBRSP-4 URL: http://tools.oasis-open.org/issues/browse/WSBRSP-4 Project: OASIS Web Services Basic Reliable and Secure Profiles (WS-BRSP) TC Issue Type: Bug Reporter: Gershon Janssen Priority: Minor Original message: https://lists.oasis-open.org/archives/ws-brsp-comment/201305/msg00001.html Issue reported by Jim Ma <ema@redhat.com>. I possibly found another test tool bug , can you please have a look again ? When the test tool analyzed the follow kerberos token message[1] , it always complains with the BSP3032 assertion failure. But from the ws-i bsp prifle.1.1 section 15, the ValuType is correct and it is almost the same with the correct example . [1] <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/oasis-wss-kerberos-token-profile-1.1#GSS_Kerberosv5_AP_REQ" wsu:Id="BST7293564EF750ED3B7213684999669821">YIICYAYJKoZIhvcSAQICAQBuggJPMIICS6ADAgEFoQMCAQ6iBwMFAAAAAACjggFhYYIBXTCCAVmgAwIBBaEPGw1XUy5BUEFDSEUuT1JHoicwJaADAgEAoR4wHBsDYm9iGxVzZXJ2aWNlLndzLmFwYWNoZS5vcmejggEWMIIBEqADAgESoQMCAQKiggEEBIIBAETe4MYI2rvOhieLjRRpx2OQnZJ5Vnx70aTENd3CZBC+1/3TQ8AO+lpNcnZ12GMOcS26GCQ6444bxEiu4fQ84ZHW4CEMSDus0k3Vvs6iCSq8w70jSYEy5x3rHdkaInObI1dP3+cMkKJqfJ6p/osqobV6g9D2zvA46CJCkEjLtLqx9bHXlef5eNaxK0GdcUngMf3F/sKngunDULPyN4iDheBPsklQU3+xLIGDmy3xp+inP7rn4EmmfbZI3wnrTpKvHmUwXYdaRnCyLx9Vckv+5LYiTDiDaG7IF6dqIyKa/HGHzSeRx8AVKYpOjxuzh1cXr43V3ya0IAERmGCCRKnO5KakgdAwgc2gAwIBEqKBxQSBwh5IJWyAHLjY5lwvOeUOboiKUgo2iB9auBM2xHqR3SYXhb//MxbU3Dy7/5m5OSVwXRD8Mrj7KBqDzdTU90sUdThFfzW6pz5jUwY22YPOYR17D9bCVCKBi/STp5hFqquryTm8TFozwqt3yuh+lht5ruRiNKLz5Qtz5CcFnvRhxX1M+cB9IfFjuWHEBVb0cmFjxLCeV5KO0AFp/4nSiga7p/UP5U6xLgQIsJgGjv4JlPcF/4Iw/um2k1h/tQ4IhGMNsrTT </wsse:BinarySecurityToken> </wsse:Security> </soap:Header> <soap:Body><ns2:DoubleIt xmlns:ns2="http://www.example.org/schema/DoubleIt"><numberToDouble>10</numberToDouble></ns2:DoubleIt></soap:Body> </soap:Envelope> [2] message_1-binarySecurityToken-BST-7293564EF750ED3B7213684999669821 Assertion: BSP3032 Result : failed Failure Message : A wsse:BinarySecurityToken element has a ValueType attribute whose value is outside the defined token profiles. Failure Detail Message: A wsse:BinarySecurityToken element has a ValueType attribute whose value is outside the defined token profiles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]