Git Product home page Git Product logo

Comments (6)

gdestuynder avatar gdestuynder commented on July 29, 2024 1

i believe that we want to stop doing that, specially for "mozillians.org repositioning"

and by that - i mean linking (we should keep doing verification of course) (just to be somewhat clear for other readers)

from mozillians.

hmitsch avatar hmitsch commented on July 29, 2024 1

^^ @akatsoulas @johngian

from mozillians.

akatsoulas avatar akatsoulas commented on July 29, 2024

Mozillians is internally linking accounts due to the account verification process. When a user verifies a new account eg LDAP, mozillians.org needs to associate the current profile with the new email thus the account linking. @gdestuynder shall we close this issue?

from mozillians.

mbransn avatar mbransn commented on July 29, 2024

i believe that we want to stop doing that, specially for "mozillians.org repositioning"

This is what I understand to be our future model and will be reflected in the architecture that I'm mapping from a proposed UX perspective now. Is this reflected in the technical architecture as well? cc @fiji-flo @hmitsch

from mozillians.

akatsoulas avatar akatsoulas commented on July 29, 2024

Totally agree for the "mozillians repositioning". My suggestion to close this issue is based on the current implementation. Right now we are missing some components and I would prefer not to re-write what we have for the current stack and then once again for the new version but rather do it once. Thoughts?

from mozillians.

fiji-flo avatar fiji-flo commented on July 29, 2024

I'm still not sure what we want to build / provide to our users here. I love the idea of being able to log into Mozillians with multiple identity providers at the same time on different devices. But most of all I want something that users understand.

However, let's find a way to do this right.

For me there are two extremes:

  1. We don't do any account linking or ratcheting. A person can have exactly one login method and that's it and any attempt to use another method ends up in the account creation flow. This would mean that we cannot use the email as user_id. And we could still allow account verification (just not via auth0).
  2. We fully support account linking and have a transparent way to control this. This means all of this is owned by auth0 and users can add/remove identities as they please. I guess this too, means we should not use the email as user_id.

from mozillians.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.