-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
URL encode / decode for uid #22
Comments
This should be fixed in Would Synapse like you throwing things like |
We have many numeric accounts in AD, but Synapse has the specifics of working with them matrix-org/matrix-synapse-ldap3#55 |
Hi, @spantaleev Logs for 2.3.0 (without encoding, error bc username seems like a url)
Logs for 2.3.1 (with encoding, error bc username seems like twice encoded)
Logs from synapse when user login by Element (with encoding no errors)
|
You're right.. I've since reverted this URL-encoding change. People with servers with normal mxids should no longer see errors during reconcilliation. Perhaps your problem is not with matrix-corporal's reconcilliation though? But with you hitting Or is reconcilliation failing on |
Reconcilliation fails on 2.3.0 without creating first user in list. M.b. something like this can solve the issue:
but I wouldn't break master once more) |
You can try that patch yourself and see if it helps with all of your users. Something is definitely fishy with these users containing Have you tried calling these APIs manually (with an admin token) to see what values they like and don't like? You could then report the issue to the Synapse repository. |
Hi. We are trying to use the UserPrincipalName entry from MS AD as the UID field. In this case Synapse replaces the @ in the username with a slash (/) and performs the url_encode operation when accessing the API. Thus, the string /%40name%2Fdomain%3Adomain is formed in the URL.
However, matrix_corporal does not do this, and when we using name/domain format names, it substitutes them directly into the URL. As a result, for "id": "@name/domain:domain" record in policy.json the API is accessed at /_synapse/admin/v1
/users/@name/domain:domain/login which results in the error code=400 wrapped=M_UNRECOGNIZED: Unrecognized request
The text was updated successfully, but these errors were encountered: