X.509 Cert Failing Triple AAA
Calling a service hosted on a XI50 box. The service is secured by a X.509 public cert, I can import the keystore and have defined the signature for the within the keystore. It fails AAA every time. ...
Forum Discussion
It is failing in the AAA step.. Attached is a dump from DP.
We do not have a requirement for BinaryToken, but other apps using WAS and JUNIT have the message working with BT ( See good messages below).
I have attached a message from another application that is working correctly.
I have also submitted this to IBM datapower team and have recieved the following response:
There is one known issue with SOAPUI and DP, and above information will help us confirm if we are encountering the same problem.
This known issue occurs when HTTP header Content-Type has params whose values are not double-quoted.
Popular tools such as SoapUI automatically generate Content-Type headers w/o the double-quotes, which causes requests to fail in DataPower.
The device adhere the RFC 822.
I did check the raw log for SOAP UI and nothing did seem to be double-quoted. I don't believe this has anything to do with the AAA
But how would I modify the content to be double-quoted to eliminate these concerns.
MIICXjCCAhygAwIBAgIERv0f1zALBgcqhkjOOAQDBQAwEjEQMA4GA1UEAxMHQ0FQVGVzdDAeFw0wNzA5MjgxNTM3NTlaFw0xNzA5MjUxNTM3NTlaMBIxEDAOBgNVBAMTB0NBUFRlc3QwggG4MIIBLAYHKoZIzjgEATCCAR8CgYEA/X9TgR11EilS30qcLuzk5/YRt1I870QAwx4/gLZRJmlFXUAiUftZPY1Y+r/F9bow9subVWzXgTuAHTRv8mZgt2uZUKWkn5/oBHsQIsJPu6nX/rfGG/g7V+fGqKYVDwT7g/bTxR7DAjVUE1oWkTL2dfOuK2HXKu/yIgMZndFIAccCFQCXYFCPFSMLzLKSuYKi64QL8Fgc9QKBgQD34aCF1ps93su8q1w2uFe5eZSvu/o66oL5V0wLPQeCZ1FZV4661FlP5nEHEIGAtEkWcSPoTCgWE7fPCTKMyKbhPBZ6i1R8jSjgo64eK7OmdZFuo38L+iE1YvH7YnoBJDvMpPG+qFGQiaiD3+Fa5Z8GkotmXoB7VSVkAUw7/s9JKgOBhQACgYEAzkwA4iRA2MxFhsBJNEVe8NZk8qJ7TZqlQZWjDO5FWL4dICH+E+ln/2xV+SEXH2xE3Cqmj2zShcg0DD7FmOUIiO+E+wd9mUmlShKFqxr81L87xf/uePOTGREgYXy7tHgG+lanzjR1QtdzwiECr+COOaukvQFYfjmu3eKswefNbR8wCwYHKoZIzjgEAwUAAy8AMCwCFEm0Iz0Oss4/jGvzF2A/9fg3QBL2AhQFjmfu1U9tV0kcdL2BU6EeN0OQLA==
IYAxeIIPAHtdrA60MHrYrm3VjAQ=
JSm0SvVIB8bl2dRdwZADTwH2Gao=
NXgrzcLFv0Qdc/qAQV+uOv2+zVxi9y0DKEIrQcpMW8yyaXjGkYiR4w==
2008-09-11T22:17:59.735Z
2008-09-11T22:22:59.735Z
011
474310285
069
We do not have a requirement for BinaryToken, but other apps using WAS and JUNIT have the message working with BT ( See good messages below).
I have attached a message from another application that is working correctly.
I have also submitted this to IBM datapower team and have recieved the following response:
There is one known issue with SOAPUI and DP, and above information will help us confirm if we are encountering the same problem.
This known issue occurs when HTTP header Content-Type has params whose values are not double-quoted.
Popular tools such as SoapUI automatically generate Content-Type headers w/o the double-quotes, which causes requests to fail in DataPower.
The device adhere the RFC 822.
I did check the raw log for SOAP UI and nothing did seem to be double-quoted. I don't believe this has anything to do with the AAA
But how would I modify the content to be double-quoted to eliminate these concerns.
