Good news! Our documentation has moved to antmedia.io/docs.

If the stream publish security filters (JWT, TOTP, etc) is not suitable for you and you want to control which stream to publish directly by your own end, you can use your own Webhook Structure for Stream Authentication. (Recommended for people with experience)

If you enable this feature, whenever a stream is initiated to publish, the server sends an HTTP request to your given Webhook address.

This request has some information regarding the stream like stream name, app name, etc.

Based on this request, you can parse and process that information on your end and send a response. If the response code is 200, the server will authorize the stream and it will start to publish if the response code is anything other than 200 the server will not allow the publishing of that stream.

You will find the red5-web.properties file in the following path

<AMS_DIR>/webapps/<AppName>/WEB-INF/red5-web.properties.

You must edit this file and add this line with your own webhook URL

settings.webhookAuthenticateURL=your-hook-URL

The feature is enabled automatically when the settings.webhookAuthenticateURL=your-hook-URL line is inserted and rebooting the server.

You can use this site https://webhook.site/ to test this feature and get your own webhook URL, however, when you send a request to that site correctly, the response code will always be 200.