JWT filters for RESTful API and Streams break AMS console?

[Doni]

Hi,

Enterprise Edition 2.3.3.1 20210609_2033

1. Enabling JWT Filter for RESTful API breaks the streams' availability in AMS console. It looks like the AMS console itself uses API calls to operate, e.g. display/create the streams and VODs, and so when I enable the JWT filter it is then blocked from doing so. Generates 403 errors because it doesn't know the token.

2. Similarly, enabling JWT Filter for Streams blocks the ability of the console to playback VODs because it uses API calls for that and doesn't know the token. 

Is there additional config I'm supposed to do to provide the console the tokens? The JWT filter otherwise works fine for client playback and client API calls, but it seems to break core console functionality.

Thanks, Doni

[Ant Media Support]

Hi Doni,
Thank you for reporting the issue.

I think this has been fixed in the snapshot v2.4 I can share the snapshot for you to check if you require.

Also, allow me some time to talk to the developer regarding any workaround/update in the v2.3.3.1 and I shall get back to you.

​

--

Best Regards,

Mohit Dubey

 

Star Ant Media Server on GitHub and get a chance to win an AMS Annual Enterprise Edition License.

On Fri, 6 Aug at 4:58 PM , Katz, Doni (US) <doni.katz@thedeal.com> wrote:

Hi,

Enterprise Edition 2.3.3.1 20210609_2033

1. Enabling JWT Filter for RESTful API breaks the streams' availability in AMS console. It looks like the AMS console itself uses API calls to operate, e.g. display/create the streams and VODs, and so when I enable the JWT filter it is then blocked from doing so. Generates 403 errors because it doesn't know the token.

2. Similarly, enabling JWT Filter for Streams blocks the ability of the console to playback VODs because it uses API calls for that and doesn't know the token. 

Is there additional config I'm supposed to do to provide the console the tokens? The JWT filter otherwise works fine for client playback and client API calls, but it seems to break core console functionality.

Thanks, Doni

--
You received this message because you are subscribed to the Google Groups "Ant Media Server" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ant-media-server+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/2b80a546-ffb2-4ebd-91f5-9e0554323f52n%40googlegroups.com.

45343:1264838

[Ant Media Support]

Hi Doni,
It will be released in this month most probably.

​

--

Best Regards,

Mohit Dubey

 

Star Ant Media Server on GitHub and get a chance to win an AMS Annual Enterprise Edition License.

On Sun, 8 Aug at 3:04 PM , Katz, Doni (US) <doni.katz@thedeal.com> wrote:

Thanks, Mohit. We're using the AWS AMI, do you know when that will be released?

Regards, Doni

From: Ant Media Support <support@antmedia.io>
Sent: Saturday, August 7, 2021 6:23 AM
To: Katz, Doni (US) <Doni.Katz@thedeal.com>
Cc: ant-media-server@googlegroups.com <ant-media-server@googlegroups.com>
Subject: [EXT] Re: JWT filters for RESTful API and Streams break AMS console?

 

Hi Doni,
Thank you for reporting the issue.

I think this has been fixed in the snapshot v2.4 I can share the snapshot for you to check if you require.

Also, allow me some time to talk to the developer regarding any workaround/update in the v2.3.3.1 and I shall get back to you.

​

--

Best Regards,

Mohit Dubey

 

Star Ant Media Server on GitHub and get a chance to win an AMS Annual Enterprise Edition License.

On Fri, 6 Aug at 4:58 PM , Katz, Doni (US) <doni.katz@thedeal.com> wrote:

Hi,

Enterprise Edition 2.3.3.1 20210609_2033

1. Enabling JWT Filter for RESTful API breaks the streams' availability in AMS console. It looks like the AMS console itself uses API calls to operate, e.g. display/create the streams and VODs, and so when I enable the JWT filter it is then blocked from doing so. Generates 403 errors because it doesn't know the token.

2. Similarly, enabling JWT Filter for Streams blocks the ability of the console to playback VODs because it uses API calls for that and doesn't know the token. 

Is there additional config I'm supposed to do to provide the console the tokens? The JWT filter otherwise works fine for client playback and client API calls, but it seems to break core console functionality.

Thanks, Doni

--
You received this message because you are subscribed to the Google Groups "Ant Media Server" group.
To unsubscribe from this group and stop receiving emails from it, send an email toant-media-server+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/2b80a546-ffb2-4ebd-91f5-9e0554323f52n%40googlegroups.com.

DISCLAIMER: The information in this email is confidential. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us by e-mail or by telephone on +44 (0) 207 779 8888 and then delete the e-mail and all attachments and any copies thereof. Euromoney Institutional Investor PLC (its subsidiaries and associates) cannot accept responsibility for the accuracy or completeness of this email as it has been transmitted over a public network. If you suspect that the email may have been intercepted or amended, please call the sender. Any views expressed by an individual in this email do not necessarily reflect views of Euromoney Institutional Investor PLC (its subsidiaries and associates). This communication is from Euromoney Institutional Investor PLC, a company registered in England and Wales under company number 954730 with registered office at 8 Bouverie Street, London, EC4Y 8AX

45343:1264838