You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the admin page to stop an application, if the application was started by another user, it is not possible to stop it. A 403 on the API is returned.
When closing your own applications, it works fine. Is this due to a change in authenticating against the API?
Everything was working fine in 3.0.2, but no longer in 3.1.0.
I haven't changed the admincontroller
I have added bootstrap to the html page
In browser I am able to navigate via https://xxx/api/proxy/e97e7bba-384c-454f-b5c8-d3fef1138974/status but the PUT request 403's.
I can see that there doesn't appear to be a difference between the 2 requests in terms of cookies or auth headers, as they are both passing the session cookie.
Also to note we are using B2C / openid
Going to investigate some more.
The text was updated successfully, but these errors were encountered:
Hi, thanks a lot for reporting this! This is a bug in the 3.1.0 release, we improved authorization in this release, but made it too strict for this part. We'll fix this soon and provide a snapshot version.
When using the admin page to stop an application, if the application was started by another user, it is not possible to stop it. A 403 on the API is returned.
When closing your own applications, it works fine. Is this due to a change in authenticating against the API?
Everything was working fine in 3.0.2, but no longer in 3.1.0.
I haven't changed the admincontroller
I have added bootstrap to the html page
The admin role is
admins
In browser I am able to navigate via
https://xxx/api/proxy/e97e7bba-384c-454f-b5c8-d3fef1138974/status
but the PUT request 403's.I can see that there doesn't appear to be a difference between the 2 requests in terms of cookies or auth headers, as they are both passing the session cookie.
Also to note we are using B2C / openid
Going to investigate some more.
The text was updated successfully, but these errors were encountered: