Subject

This memo presents what happens when an existing HBP user tries to login to a service which uses Collaboratory 2 authentication (e.g. https://wiki.ebrains.eu)

Case 1: User has an account in Collaboratory 1 but not in Collaboratory 2

Case 1.1: User has a personal (non-institutional) email, e.g. at gmail.com

When the user attempts to login, the login is rejected. This username is unknown in Collaboratory 2, and Collaboratory 1 authentication is not checked because it's an unauthorized email address in the Collaboratory 2 space.

Possible actions:

• The user registers for a new account by clicking "Getting Access" and uses an institutional email address. Or,
• The user asks Support to create exceptionally an account with a personal email and motivates the request.

Case 1.2: User has an institutional email, e.g. at epfl.ch

Case 1.2.1: User has an SGA2 accreditation in the Collaboratory 1

At first login, the user will have to verify the email address linked to the user account in order to login.

Case 1.2.2: User does not have an SGA2 accreditation in the Collaboratory 1

A user account will be automatically created in the Collaboratory 2, but the user will be denied access to the service. The image below shows the message displayed to the user. Pas de validation d email ici?

Possible action :

• If the user is an HBP member from an institution in the HBP Consortium, the user can request SGA2 accreditation in the Collaboratory 1 and then try to login again. Or,
• in iam, put the user in his institution group or add manually to the user the role collaboratory_member

Case 2 : User has a Collaboratory 2 account

If the user has a Collaboratory 2 account, access is completely independent of having a Collaboratory 1 account, and of having an SGA2 accreditation there or not.

At first login, the user will have to verify the email address linked to the user account in order to login.

We already have some users with a personal email for historical reasons (automated import of accredited SGA2 users from Collaboratory 1). These users all belong to the unit called imported. Access to the service then depends on the service itself. The imported unit has for now (exceptionally) the role collaboratory_member so its members have access to the Collaboratory services, e.g. at https://wiki.ebrains.eu.

This has been tested: personal emails properly receive the verification email and access is then authorized.

There is no possible scenario currently for users with personal email to not be in the imported group, so they should all have access to wiki, except for those handmade created after a support request. Users created from a support request should be put in the appropriate unit with the appropriate access case by case.