simpleidserver / SimpleIdServer

OpenID, OAuth 2.0, SCIM2.0, UMA2.0, FAPI, CIBA & OPENBANKING Framework for ASP.NET Core
https://simpleidserver.com/
Apache License 2.0
719 stars 94 forks source link

Can't add new ApiResource to a scope in a non-master realm #569

Closed mshwf closed 4 months ago

mshwf commented 1 year ago

I'm facing this problem in the project I'm working on, before reporting the issue I tried the same steps on the demo website: https://website.simpleidserver.com/

Steps to reproduce: Go to the demo administration website> Activate 'test' realm> Scopes> Select 'test' Scope Try 'Add API resource'

Actual behavior: Nothing happens, and this error shows up in the console:

Uncaught (in promise) Error: Cannot send data if the connection is not in the 'Connected' State. at Nt.send (blazor.server.js:1:54577) at Ft._sendMessage (blazor.server.js:1:71300) at Ft._sendWithProtocol (blazor.server.js:1:71341) at Ft.send (blazor.server.js:1:71449) at Object.beginInvokeDotNetFromJS (blazor.server.js:1:134874) at w (blazor.server.js:1:2167) at C.invokeMethodAsync (blazor.server.js:1:4035) at blazor.server.js:1:11583 at T (blazor.server.js:1:11761) at I (blazor.server.js:1:11552)

Expected behavior: The add new resource form shows up and I can add new API Resource (like I can when the 'master' realm is activated)

simpleidserver commented 1 year ago

The error displayed in the console application does not have an impact. When a websocket connection cannot be established between the Blazor Server and the Javascript Client, then Long Polling will be used. I attempted to replicate the issue on the website website.simpleidserver.com without success :( The Api Resource is added at the end of the table. Could you please try again?

Kind regards, SID

mshwf commented 1 year ago

Thanks for your help, appreciate it. I couldn't do better than recording the issue, so here it is. I also tried on different browser/device (not sure if this could help) but still the same behavior.

SID_add_api_resource

simpleidserver commented 1 year ago

Indeed there is an issue :( It is already fixed in the branch release\4.0.4.

KR,

SID