Replies: 1 comment
-
You need to pass the httpCookieStore to your HTTP requests. This way /settings/appName route will know that you are authenticated. Example code snippet for java:
You must pass httpCookieStore(BasicCookieStore httpCookieStore = new BasicCookieStore(); By the way username password authentication is for testing purposes. I highly recommend you to enable REST API JWT Filter through app settings and using it. Generate a long term JWT, put it to your server .env and pass it to the HTTP reqs. |
Beta Was this translation helpful? Give feedback.
-
Hi Ant Media Team,
I'm experiencing an issue with the /rest/v2/applications/settings/{appName} API. Here's the situation:
I have successfully used the following two APIs without any issues:
/rest/v2/users/initial
/rest/v2/users/authenticate
However, when I attempt to use the settings API (/rest/v2/applications/settings/{appName}), I receive a 403 Forbidden error.
Here is a summary of my setup:
API endpoint: http://localhost:5080/rest/v2/applications/settings/{appName}
Server setup: Running on Apache Tomcat, using Ant Media version [specify version].
Authentication seems to work fine for user-related APIs, but the settings API is blocked.
The log output shows:
bash
Sao chép mã
Configure settings for app failed. Detail: 403 Forbidden from POST http://localhost:5080/rest/v2/applications/settings/LiveApp
What I've tried:
Ensured that the application name is correct.
Confirmed that authentication succeeds for the user APIs.
Checked permissions and roles associated with the authenticated user.
Any help or guidance on resolving this issue would be greatly appreciated.
Here is the corresponding code for making the API request:
Beta Was this translation helpful? Give feedback.
All reactions