ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 0 replies, has 1 voice, and was last updated by  jordiacsense 1 year, 4 months ago.

  • Creator
    Topic
  • #18134

    jordiacsense
    Participant

    Hi,

    I’m trying to generate my own WSSE header with each request I’m making towards my API. However when creating my header I seem to notice that my nonce is different and that my passwordDigest is way longer then in the examples and in the WSSE header creation tool:

    – (doc) https://www.orocrm.com/documentation/index/current/cookbook/how-to-use-wsse-authentication
    – (tool) http://www.teria.com/~koseki/tools/wssegen/

    What do I do ?

    I’m creating a nonce myself by generating an UUID and base64 encrypt it.

    Then I create the timestamp. Afterwards I’m creating the password digest by decoding the nonce from base64 (this part confuses me somewhat, how can you decode the nonce when it is never encoded?[docs]). Then I add the timestamp and API key to the string, this string I sha1 encrypt. After that I encrypt it another time with base64.

    This is bassicaly my output:

    nonce String “Mzc4MEQ3N0UtMTU0RC00RTdBLUFENTMtRDhCMjQ5M0Y4RDE4”
    passwordDigest String “NGZmY2IxZmNjNTkwNGJmNGU0YWYwMDA2OWQxNWE4NDFjZmNhNTE1ZQ==”

    Are there any requirements on the length of the nonce or password or whatsoever? Because that is the thing that differs form the documentation and tool. Or am I doing something else completely wrong?

You must be logged in to reply to this topic.