API Connect

API Connect

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.


#API Connect
#Applicationintegration
#APIConnect
 View Only
  • 1.  Unable to verify the signed request on DataPower

    Posted 09/11/23 03:03 AM

    On Data Power V10 virtual appliance, 

    I have created an MPGW service for sign and verify.
    I am able to sign the message using our public and private key and made another rule to verify that particular message  using public key on same processing policy but it is throwing below error
    "*RSA signature did not verify* (from client)".

    - The configuration of Sign Action is :

    1. XML security.
    2. Envelope Method equal Enveloping Method.
    3. Message type equal Raw XML Document, including SAML for Enveloped.
    4. Add in Key field the private key.
    5. Add in certificate field the certificate.


    - The configuration of Verify Action is :

    1. Signature Verification Type equal RSA/DSA Signatures
    2. Add in certificate field the certificate.

    Note: The certificate key are proper pair, the message send to verify is not altered i am directly sending the whole signed msg in verify req body

    Sign :http://192.168.31.151:2007/sign

    Verify: http://192.168.31.151:2007/verify

    Any help to solve this issue is highly appreciated.



    ------------------------------
    Ashwin
    ------------------------------

    Attachment(s)

    zip
    Sign-Verify-MPG (1).zip   849 KB 1 version
    txt
    sign-verify req-res.txt   8 KB 1 version


  • 2.  RE: Unable to verify the signed request on DataPower

    Posted 09/11/23 09:39 AM

    Hi Ashwin,
    This is a DataPower not an API Connect issue.  You should post your question in the DataPower community forum at https://community.ibm.com/community/user/integration/communities/community-home/digestviewer?communitykey=b13f4693-16ee-422b-9d0b-f5262e25426f.

    Just at a quick glance I don't see anything that jumps out at me with your configuration.  I'd set your log level to debug and perhaps it will provide some more information on your issue.
    Best Regards,

    Steve



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM
    ------------------------------