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
Currently, Element Web only supports signing up for Matrix-based authorisation.
This task is use the information about whether the homeserver supports OIDC to decide whether to offer sign-up via that, and then to send the user to the OIDC web UI for sign-up if the user so chooses.
TODO: should we also offer legacy sign-up, or do we ONLY offer OIDC if it's available?
Do not query for registration methods/show error
Use OIDC discovery openid-configuration, check for create in prompt_values_supported
Where supported, add a register button that starts an OIDC auth flow with prompt=create
The text was updated successfully, but these errors were encountered:
Support sign-up via native OIDC in Element Web. Refer to https://areweoidcyet.com/client-implementation-guide/ for guidance. (You will need to find out what OIDC is before you can understand it.)
You will almost certainly need to break this story up into smaller parts before implementing it.
Below, we assume that #25392 is already done.
Currently, Element Web only supports signing up for Matrix-based authorisation.
This task is use the information about whether the homeserver supports OIDC to decide whether to offer sign-up via that, and then to send the user to the OIDC web UI for sign-up if the user so chooses.
TODO: should we also offer legacy sign-up, or do we ONLY offer OIDC if it's available?
create
inprompt_values_supported
prompt=create
The text was updated successfully, but these errors were encountered: