Skip to main content
Solved

HTTP message signing

Bas
Vanguard
Forum|alt.badge.img+3
  • BasVanguard
  • Vanguard
  • 19 replies

For a client we're currently scoping the development of a new integration to their system.

This platform offers data exchange services between multiple parties. Their service is API based with the actual message traffic being send in XML. Because of the type of data being processed security is extremely important to all parties involved.

It is therefor mandatory to sign all outgoing messages. Their documentation contains the following example on how to do this within the context op postman.

openssl dgst -sha256 -sign ‘[private_key_name].key’ -out ‘[signature_name].sha256’ ‘[message_name].xml’

If then asks you to base64 encode the signature_name.sha256 and message_name.xml before transmission.

How would we approach this from within a Thinkwise environment?

Best answer by Mark Jongeling

Hi Bas,

Within the Thinkwise platform we currently don't have a way to do this. After some research of our own we found some interesting ways of approaching this.

  1. Maybe it's possible by using SQL Server certificates: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-certificate-transact-sql?view=sql-server-ver15 and https://docs.microsoft.com/en-us/sql/t-sql/functions/signbycert-transact-sql?view=sql-server-ver15
  2. If that doesn't work a CLR procedure in SQL Server might be a solution. Although this is less than ideal.
  3. If the SQL Server crypto functions don't give the desired result, maybe it's possible with OLE Automation: https://www.example-code.com/sql/xmldsig_sign_dsa.asp

All of these suggestions need some more and deeper research. Does this help?

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Mark Jongeling
  • Administrator
  • 3959 replies
  • Answer
  • May 25, 2021

Hi Bas,

Within the Thinkwise platform we currently don't have a way to do this. After some research of our own we found some interesting ways of approaching this.

  1. Maybe it's possible by using SQL Server certificates: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-certificate-transact-sql?view=sql-server-ver15 and https://docs.microsoft.com/en-us/sql/t-sql/functions/signbycert-transact-sql?view=sql-server-ver15
  2. If that doesn't work a CLR procedure in SQL Server might be a solution. Although this is less than ideal.
  3. If the SQL Server crypto functions don't give the desired result, maybe it's possible with OLE Automation: https://www.example-code.com/sql/xmldsig_sign_dsa.asp

All of these suggestions need some more and deeper research. Does this help?

 

"Wake me up before you low-code"
Bas
Vanguard
Forum|alt.badge.img+3
  • BasVanguard
  • Author
  • Vanguard
  • 19 replies
  • September 29, 2021

Because of another issue we had we already needed to use an AWS LAMDA function, it ended up being easier to have this lamda function expose an api that returned the required signature for a specific message.

I think we didn’t get it to work within SQL server because we lacked knowledge and authorisation to create and work with certificates.

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings