AXIS D1110 Video Decoder 4K APIs http/s and other ways

[matyasdelcampo]

Dear Axis community.

I’m trying to control d1110 decoder with third party control system (Crestron). I have done some testing and debugging and can’t find a way how to make it work.

I can control d1110 with postman with no problem:

1-https. The problem is postman can ignore invalid certificates and Crestron can’t. So if I wanna use https I need to make certificates right. But I do not have dns server on the local network and all certificates on d1110 use hostname. So either I need dns server or create new certificates with ip address instead of hostname. I have tried to create cert but it does not work.

2-http: with postman I can controller it using digest authentication but Crestron can’t integrate digest authentication only the basic authentication. Is there any way how to change the digest to basic on decoder for http?

Is there any other way how to controll this device ? Like modbus or tcp/ip(sort of telnet protocol)?

Thanks for any idea

Matyáš

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[Cacsjep]

You can change the boa policy via param.cgi, regarding to https, I mean unsecure but you can use http. The question would be how creation does validate the cert. I don't know what this is but when it's windows or so you may need to add the trusted CA certificate to the windows store or crestion CA store. We had an windows app called ASA where you can simply create a local PKI. May this helps out. In general you need an CA that both devices trust, so on CA where you then sign your camera https cert. On crestion side the ca needs to be somewhere for validation. SAN entries should include IP address. Real question is how crestion validate it.

[Cacsjep]

@matyasdelcampo http://10.0.0.47/axis-cgi/param.cgi?action=update&root.Network.HTTP.AuthenticationPolicy=basic

[Cacsjep]

@matyasdelcampo contact me if you need help: c.acs@commend.at sure we find a way todo this, also may i could very fast implement a TCP trigger or other trigger that Crestron support to our Missing Features ACAP =)

[rocky-ji]

You can change the authentication via web GUI - system-plain config-search authentication and change it to basic.

for other protocol, if you can write ACAP, then it should also be possible, but at least you need write some code to make it work:
Here is one modbus ACAP
https://github.com/AxisCommunications/modbus-acap

[vivekatoffice]

Hi @matyasdelcampo ,
I agree with @rocky-ji and @Cacsjep's suggestion to move to HTTP (Basic Authentication).

But if you have the option to run middleware or a server system in a project, you can use the API Proxy method with HTTP/HTTPS Digest Auth.

Image Reference

[vivekatoffice]

Feel free to re-open it OR share the solution/alternative/comment if already resolved👁️‍🗨️