frail plume
Hi all, the Appwrite 1.6.0 cloud update has broken the OpenID Connect provider. The server responds with a 500 internal server error. I am testing with Flutter using version 13.0.0 of the SDK. Authentication was working before the latest cloud update. It looks like this is the url that returns the 500 error 'https://cloud.appwrite.io/v1/account/sessions/oauth2/oidc/redirect'. Any help would be appreciated.
old elbow
Hi all, the Appwrite 1.6.0 cloud update has broken the OpenID Connect provider. ...
What's your project ID?
frail plume
@old elbow Hi, I'm currently testing on project with ID: playground-for-flutter-1
old elbow
@frail plume Is this solved now?
frail plume
<@876513364434649148> Is this solved now?
No the issue still exists since the latest update. It is also worth noting that there is an additional issue with the Open ID connect provider, the Oidc.php file sends the scopes in the token endpoint as seen here https://github.com/appwrite/appwrite/blob/0e2679f07b79ec55a7a82dda0ed683f4eff2b640/src/Appwrite/Auth/OAuth2/Oidc.php#L73. I would assume that with oidc you would only want to place the scopes in the authorisation endpoint, otherwise you're essentially suggesting that after the user has requested authorisation with a specific set of scopes, they can have a token returned with potentially a completely different access policy. I have noticed that oidc server packages completely refuse requests where the scopes are in the token endpoint as seen here: https://github.com/openiddict/openiddict-core/blob/d4c05e2e236c9fe6ecc2c97570b1cde7fac1a8ea/src/OpenIddict.Server/OpenIddictServerHandlers.Exchange.cs#L798
old elbow
No the issue still exists since the latest update. It is also worth noting that ...
Do you can open a GitHub issue for this?