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

ProConnect - User authentification cases #155

Open
Gaetanbrl opened this issue Dec 18, 2024 · 0 comments
Open

ProConnect - User authentification cases #155

Gaetanbrl opened this issue Dec 18, 2024 · 0 comments

Comments

@Gaetanbrl
Copy link

Gaetanbrl commented Dec 18, 2024

As part of ProConnect developments,

It is necessary to manage the steps when a user already exists or needs to be created.

ProConnect (OpenId /userinfos) return many user's informations.

Therefore, only EMAIL and SIRET will be used to ease compare and avoid over-complex cases.

Description

  • If user use ProConnect, we will control EMAIL to search user in geOrchestra
  • if user already exists, we just link geOrchestra user with user authentified via ProConnect (roles and org)
  • If email not exists, we create a new user
  • If ProConnect SIRET exists in geOrchestra's org, we just link (existing) organisation < > user
  • If SIRET not exists, user needs to create a new organization (see step 2 - ProConnect - User and organization mapping #158)

Don't hesitate to reply or complete this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant