In reply to @max:kamax.io

can you tell me the exact step by step from the moment the link is clicked for both scenarios:

• what is actually happening
• what you expect to see

I'll need the step-by-step in both. Clearly it's a matter of expectations that maybe can be resolved by configuration, or maybe it's just a misunderstanding on what is happening

Jason Morgan: thank you for the detailed walkthrough, I see two things here:

1. Riot v1.x has issue handling the links from email verification in a meaningful way from its own link. The fact that mxisd sends back to the Riot client is because the client has given a "Next URL" after validation, but Riot doesn't handle its own URL right. Regardless, there should be the initial window/tab from step 5 which can be used and will bring Alice to the landing "logged in" page. The 2nd tab will just look like it failed.
2. The invite remaining unresolved is most likely due to an issue with not having an Identity Store configured to resolve such associatation. It depends where Alice registered the account. If it was on the same homeserver as the invite, you'll need at least the Synapse Identity Store configured, since that's where the info will live about the mapping.
3. The email from the invite and from the registration must exactly match. Your walkthrough make it look like that's the case, but it might not be with your real user.

In reply to @max:kamax.io

Jason Morgan: thank you for the detailed walkthrough, I see two things here:

1. Riot v1.x has issue handling the links from email verification in a meaningful way from its own link. The fact that mxisd sends back to the Riot client is because the client has given a "Next URL" after validation, but Riot doesn't handle its own URL right. Regardless, there should be the initial window/tab from step 5 which can be used and will bring Alice to the landing "logged in" page. The 2nd tab will just look like it failed.
2. The invite remaining unresolved is most likely due to an issue with not having an Identity Store configured to resolve such associatation. It depends where Alice registered the account. If it was on the same homeserver as the invite, you'll need at least the Synapse Identity Store configured, since that's where the info will live about the mapping.
3. The email from the invite and from the registration must exactly match. Your walkthrough make it look like that's the case, but it might not be with your real user.

In reply to @jasonm:matrix.cambsac.org.uk
1: Riot 1.1.2, I was not aware of Riot 2?

In reply to @jasonm:matrix.cambsac.org.uk
1: Riot 1.1.2, I was not aware of Riot 2?

In reply to @max:kamax.io

Jason Morgan: thank you for the detailed walkthrough, I see two things here:

1. Riot v1.x has issue handling the links from email verification in a meaningful way from its own link. The fact that mxisd sends back to the Riot client is because the client has given a "Next URL" after validation, but Riot doesn't handle its own URL right. Regardless, there should be the initial window/tab from step 5 which can be used and will bring Alice to the landing "logged in" page. The 2nd tab will just look like it failed.
2. The invite remaining unresolved is most likely due to an issue with not having an Identity Store configured to resolve such associatation. It depends where Alice registered the account. If it was on the same homeserver as the invite, you'll need at least the Synapse Identity Store configured, since that's where the info will live about the mapping.
3. The email from the invite and from the registration must exactly match. Your walkthrough make it look like that's the case, but it might not be with your real user.

Hello! First of all, thank you so much for this piece of software! :)

Maybe you can answer a question for me. I use mxisd on different servers, after updating mxisd I get the following error message when deleting a user:

{
    "errcode": "M_UNKNOWN",
    "error": "Failed to remove threepid from ID server"
}

I'm not even sure if it's mxisd. But maybe you have an idea!