-
From the Onvif Documents, formula to get the Password Digest was obtained as follows : I have ref camera, with the following details : Im not able to get the Digest with the above details using online b64encode/b64decode tools Is there any detailed steps how to generate this Digest value when Nonce, Date and Password is known to us? |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 1 reply
-
Where did you get that formula? I do not think that is not how one calculates a digest response. |
Beta Was this translation helpful? Give feedback.
-
You can use a third party software package such as gSoap (Genivia) to allow you to make SOAP calls in Digest or Username Token to an ONVIF device. The package can be purchased with a commercial license or if you are a student or non-commercial entity you could download an open source version which has some restrictions. Finally for full references to the "Username Token" they are documented within the "ONVIF Core Specification" , Oasis document (http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf) and rfc2617 specification (https://datatracker.ietf.org/doc/html/rfc2617). |
Beta Was this translation helpful? Give feedback.
-
Sorry closed by accident. |
Beta Was this translation helpful? Give feedback.
-
Gsoap toolkit was used to generate the codes, which enabels the communication with Digest and Username Token. Password Digest : 3mF2UUI1049sVDGRmhezP+i2x0s= Password of the device : admin1234# as per the document, digest formula is like Then a/c to the device details, this doesnt match with the Password Digest from the CLients. Is this the way, password digest is found, Im working on the server side, to check whether the Password given from the client is valid. Not able to obtain the password digest correctly. Am doing missing out anything. Please help on this. |
Beta Was this translation helpful? Give feedback.
-
I think you are looking at the wrong RFC. Digest has a few, but the one mentionned in the ONVIF documentation is https://datatracker.ietf.org/doc/html/rfc2617 which uses MD5 for the hashing algorithm and not SHA-1. |
Beta Was this translation helpful? Give feedback.
-
Will check that and get back to you again. |
Beta Was this translation helpful? Give feedback.
-
Yep, if you read my comments above I said the same as Jean-Francois and also supplied the Oasis document for WS_UsernameToken. He is correct not "SHA1" but "MD5". You said you used the gSoap engine. There are various plugin's available to handle UsernameToken such as "http_da" (https://www.genivia.com/doc/httpda/html/httpda.html) which provide methods to handle WSSE as part of ONVIF Soap Requests. |
Beta Was this translation helpful? Give feedback.
You can use a third party software package such as gSoap (Genivia) to allow you to make SOAP calls in Digest or Username Token to an ONVIF device. The package can be purchased with a commercial license or if you are a student or non-commercial entity you could download an open source version which has some restrictions.
Finally for full references to the "Username Token" they are documented within the "ONVIF Core Specification" , Oasis document (http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf) and rfc2617 specification (https://datatracker.ietf.org/doc/html/rfc2617).