Skip to content
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

m.login.password identifier #66

Closed
tpeacock19 opened this issue Apr 16, 2022 · 4 comments · Fixed by #117
Closed

m.login.password identifier #66

tpeacock19 opened this issue Apr 16, 2022 · 4 comments · Fixed by #117
Assignees
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@tpeacock19
Copy link

I'm not sure if you've experienced this, but when using Conduit I get an error with the current login flow. The below diff is current with the latest protocol identifier types seen here.

diff --git a/ement.el b/ement.el
index b5e6238..9cec1c0 100644
--- a/ement.el
+++ b/ement.el
@@ -203,7 +203,9 @@ the port, e.g.
                () (pcase-let* (((cl-struct ement-session user device-id initial-device-display-name) session)
                                ((cl-struct ement-user id) user)
                                (data (ement-alist "type" "m.login.password"
-                                                  "user" id
+                                                  "identifier"
+                                                  (ement-alist "type" "m.id.user"
+                                                               "user" id)
                                                   "password" password
                                                   "device_id" device-id
                                                   "initial_device_display_name" initial-device-display-name)))

This also could allow for users to potentially login with a 3pid using m.id.thirdparty in place of m.id.user, but that would of course require more logic.

@alphapapa
Copy link
Owner

Thanks, I didn't know they had changed that in the spec. I'd guess that you might want to report that to Conduit as well, because they might be excluding some older clients by requiring this. Anyway, I'll apply this change soon. :)

@alphapapa alphapapa self-assigned this Apr 21, 2022
@alphapapa alphapapa added bug Something isn't working enhancement New feature or request labels Apr 21, 2022
@alphapapa alphapapa added this to the 1.1 milestone Sep 9, 2022
@viiru-
Copy link
Contributor

viiru- commented Feb 8, 2023

This appears to have changed between spec version r0.3.0 ( https://matrix.org/docs/spec/client_server/r0.3.0.html#password-based ) and r0.4.0 ( https://matrix.org/docs/spec/client_server/r0.4.0.html#password-based ). Conduit claims the following version support: "versions":["r0.5.0","r0.6.0","v1.1","v1.2"], so it not supporting the r0.3.0 login API (which is the only one supported by Ement) seems to match what is documented.

@alphapapa alphapapa modified the milestones: 0.4, 0.6 Feb 10, 2023
@alphapapa
Copy link
Owner

@viiru- Thanks for researching that. I'll target this for the 0.6 release.

@alphapapa
Copy link
Owner

Thanks to all for your help with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants