Change Details

As an editor I want to edit on the repo with the same credentials as on the client in order to not leak personally identifiable information. **Problem:** We want to ensure that the edit that is made on the repo via the Wikidata Bridge is made under the same account as the user uses on the client. We want to especially avid the case where the editor is logged in on the client but edits as an IP on the repo as that is leaking private information. **BDD** GIVEN AND WHEN AND THEN AND **Acceptance criteria:** * **Open questions:** * Is this all already done from the security-side with using assertuser? * What happens if the client user has not logged into the repo before?

As an editor I want to edit on the repo with the same credentials as on the client in order to not leak personally identifiable information. **Problem:** We want to ensure that the edit that is made on the repo via the Wikidata Bridge is made under the same account as the user uses on the client. We want to especially avid the case where the editor is logged in on the client but edits as an IP on the repo as that is leaking private information. **BDD** GIVEN AND WHEN AND THEN AND **Acceptance criteria:** * **Open questions:** * Is this all already done from the security-side with using assertuser? * What happens if the client user has not logged into the repo before? * What are the possible reasons when centralauth doesn't log you in to the repo? (see for example https://phabricator.wikimedia.org/T231209#5445076) * What are possible ways out of these cases? * What options do we have for recovery on the client after assertuser fails?

As an editor I want to edit on the repo with the same credentials as on the client in order to not leak personally identifiable information. **Problem:** We want to ensure that the edit that is made on the repo via the Wikidata Bridge is made under the same account as the user uses on the client. We want to especially avid the case where the editor is logged in on the client but edits as an IP on the repo as that is leaking private information. **BDD** GIVEN AND WHEN AND THEN AND **Acceptance criteria:** * **Open questions:** * Is this all already done from the security-side with using assertuser? * What happens if the client user has not logged into the repo before? * What are the possible reasons when centralauth doesn't log you in to the repo? (see for example https://phabricator.wikimedia.org/T231209#5445076) * What are possible ways out of these cases? * What options do we have for recovery on the client after assertuser fails?