Wowza Community

More secure authentication for Wowza Rest API

I am using Wowza Streaming Engine but managing it through Rest API.

I want to make my restAPI secure and invulnerable. I have gone through multiple authentication methods like basic, digest, remote HTTP, etc in the documentation. And out of them, I found remote HTTP is the most secure way of authentication.

I am able to successfully integrate my Wowza manager login through remote HTTP. But I am unable to authenticate my RestAPI through it. I am able to authenticate restAPI using only 2 methods - basic and digest.

I found your very old post of OCT’15 about it - Securing Rest Interface wowza. Is it still the true or you have extended your support for remoteHTTP?

Thank you for sharing what steps and docs you’ve already researched. I believe this is what you’re looking for though:

This is the section you want and it has sample code:

Use remote HTTP authentication

Remote HTTP authentication goes one step further than digest HTTP authentication: It uses a remote server to generate a custom digest value from a shared secret. That digest value is then included in an authorization header of your HTTP request to the REST API.

But let me know if you’ve already tried that and it didn’t work @Pankil_Thakkar

Yes, I have already referred to this link. But it was not useful for implementing --remotehttp method in Wowza streaming engine REST API.

Here is demo API I am posting which I am currently using in my applicaiton with --basic authentication.

To get All Applications

curl -X GET \
--basic -u 'username:password' \
-H 'Accept:application/json; charset=utf-8' \
-H 'Content-Type:application/json; charset=utf-8' \

Actually, I want to use --remotehttp instead of --basic or --digest in Rest API. When I hit this API using the --basic or --digest method whichever is mentioned in Server.xml, it gives me a proper response in JSON.

But when I change it to --remotehttp, it gives me error like “–remotehttp is an unknown option”

Can you please help me in this?

What error do you get, make sure the remote endpoint is reachable and is returning appropriate http response.