-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New users can't login (register?) #453
Comments
Thanks to report the issue. I can't reproducte the issue on my side so it's a bit more complex. What is the result of |
|
And |
USER1 and USER2 are two old users who have a matrix account from before the update. |
Do you mean on domain.tld/yunohost/sso ? |
Exactly. |
are you sure that the user have the permission to access to synapse (with (note we can discuss with matrix it might be easier) |
|
If you try this from the new user |
Well actually it's the same for old user also. The log I mention wasn't nginx log but |
Well I think if there are a redirection to the yunohost sso it's more an issue on nginx/sso side than on synapse it's why I would like the log of nginx to understand why there are this redirection. Can you share me also the content of |
Je remarque que NEWUSER1 and NEWUSER2 are not listed in
and also some old users aren't listed neither. Maybe I'll try (if I can) if thoose old user account can connect or not. |
Indeed, if I try to login in app.element.io with CAS on matrix.domain.tld with one of the old user account not listed in
it doesn't work neither. I'd like to add also the fact that in
are actually listed two very old redirection unused today (i removed them before copy/paste). So it sounds like |
Well it depends. Since a long time synapse don't manage this file. So either you have a really old install and there still are some dirty thing linked to the history or you did a customization. |
I have a very old installation I guess but no customization. What should I do? Can I delete Well actually, if synapse don't manage it anymore, I guess yunohost won't generate any as everything is related to synapse in it except
which are also very old redirection unused today anyway. So it sounds like a heritage unnecessary. |
No the If you don't need any customization you can just put |
Thank you @Josue-T . |
Describe the bug
Old users can connect to synapse thanks to Element app and CAS.
New created user can't login thanks to CAS.
Context
Steps to reproduce
Create a new user.
Connect to SSO with this user.
Go to app.element.io
Choose our synapse server adress
Click on "Continue with CAS"
Reach to the SSO screen
Expected behavior
Be redirected to an url like
/_matrix/client/r0/login/cas/ticket?redirectUrl=
as it is the case for old accounts who have already used synapse server in the past.Logs
in logs, I can see that when I attempt to login with new account :
and this when I login with old account :
The text was updated successfully, but these errors were encountered: