Axis cameras' replay attack protection thwarts initialization

[GoogleCodeExporter]

> What steps will reproduce the problem?
1. Instantiate an OnvifDevice against an Axis camera (M5014). Fails due to 
authorization failure calling getCapabilities() in init().

> What is the expected output? What do you see instead?
Expected initialization to succeed.

> What version of the product are you using? On what operating system?
Latest source from SVN running from Eclipse on Windows


> Please provide any additional information below.

The initialization fails because Axis cameras check the created date in the 
SOAP message, and compare it against its internal clock to prevent replay 
attacks. (This protection can be disabled in the camera's configuration, but i 
would like to make connectivity work with minimal effort from the user.) 
Initialization should include a call to GetSystemDateAndTime, and then use the 
difference between the local clock and the camera's clock in the creation of 
the Created time for authentication purposes.

Original issue reported on code.google.com by mlohbih...@gmail.com on 5 Nov 2014 at 3:16

[GoogleCodeExporter]

Note: I will be working on a fix for this. Let me know if you want me to 
provide it.

Original comment by mlohbih...@gmail.com on 5 Nov 2014 at 3:17

[GoogleCodeExporter]

Good idea.

Original comment by i...@milgo.de on 16 Dec 2014 at 12:20

• Changed state: Accepted

[GoogleCodeExporter]

Thanks. Note that i have already made this change, as well as numerous others. 
I would be happy to contribute these back.

Original comment by matt...@lohbihler.me on 16 Dec 2014 at 2:42

[GoogleCodeExporter]

I added you to project committers.

Original comment by i...@milgo.de on 16 Dec 2014 at 3:11