We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the file packages/matrix-identity-server/src/3pid/bind.ts, there is a TODO comment on line 81 that needs to be addressed:
// TODO : hook for any pending invite and call the onbind api : https://spec.matrix.org/v1.11/client-server-api/#room-aliases
The current implementation lacks functionality to handle pending invites and call the onbind API as specified in the
Implement a function to create a signature using the generated key pair.
Make a POST request to /_matrix/identity/v2/sign-ed25519 to sign the data.
matrix spec
Implement a function to send a PUT request to /_matrix/federation/v1/3pid/onbind on the recipient's Matrix server.
Ensure the request includes the necessary payload, such as the signed data and relevant 3PID information.
The text was updated successfully, but these errors were encountered:
guimard
pm-McFly
No branches or pull requests
Description:
In the file packages/matrix-identity-server/src/3pid/bind.ts, there is a TODO comment on line 81 that needs to be addressed:
// TODO : hook for any pending invite and call the onbind api : https://spec.matrix.org/v1.11/client-server-api/#room-aliases
Problem:
The current implementation lacks functionality to handle pending invites and call the onbind API as specified in the
Tasks:
Create Long-Term Key Pairs:
Create Signature:
Implement a function to create a signature using the generated key pair.
Make a POST request to /_matrix/identity/v2/sign-ed25519 to sign the data.
Call onbind API:
matrix spec
Implement a function to send a PUT request to /_matrix/federation/v1/3pid/onbind on the recipient's Matrix server.
Ensure the request includes the necessary payload, such as the signed data and relevant 3PID information.
The text was updated successfully, but these errors were encountered: