Wiki source code of Access to Collaboratory
                  Last modified by mmorgan on 2021/09/17 12:32
              
      Show last authors
| author | version | line-number | content | 
|---|---|---|---|
| 1 | == Subject == | ||
| 2 | |||
| 3 | This memo is intended for users having trouble to connect to Collaboratory 2 services. It presents what happens when a user tries to login to a service which uses Collaboratory 2 authentication (e.g. [[https:~~/~~/wiki.ebrains.eu>>https://wiki.ebrains.eu]]) | ||
| 4 | |||
| 5 | === __**Case 1:** User has an account in Collaboratory 1 but not in Collaboratory 2__ === | ||
| 6 | |||
| 7 | ==== __**Case 1.1:**__ User has a personal (non-institutional) email, e.g. at gmail.com ==== | ||
| 8 | |||
| 9 | 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. | ||
| 10 | |||
| 11 | [[image:Screenshot 2020-04-29 at 16.24.42.png||height="278" width="549"]] | ||
| 12 | |||
| 13 | |||
| 14 | **Possible actions:** | ||
| 15 | |||
| 16 | * The user registers for a new account by clicking "Getting Access" and uses an institutional email address. Or, | ||
| 17 | * The user asks Support to create exceptionally an account with a personal email and motivates the request. | ||
| 18 | |||
| 19 | ==== __**Case 1.2:**__ User has an institutional email, e.g. at epfl.ch ==== | ||
| 20 | |||
| 21 | At first login, the user will have to verify the email address linked to the user account in order to login. Then they will have access to the Collaboratory 2 services. | ||
| 22 | |||
| 23 | [[image:Screenshot 2020-04-29 at 16.33.11.png||height="311" width="702"]] | ||
| 24 | |||
| 25 | |||
| 26 | === __**Case 2 :** User wants to register in Collaboratory 2__ === | ||
| 27 | |||
| 28 | ==== __**Case 2.1:**__ User has a personal (non-institutional) email, e.g. at gmail.com, or an institutional email that is not recognized, e.g. at acme.com. ==== | ||
| 29 | |||
| 30 | Registration requires an institutional email. Exceptions can be made and an account request must be submitted to support. | ||
| 31 | |||
| 32 | [[image:1588614826519-874.png||height="201" width="711"]] | ||
| 33 | |||
| 34 | |||
| 35 | **Possible actions:** | ||
| 36 | |||
| 37 | * If you think your institution should be authorized, contact support and we will review whether the institution should be added. | ||
| 38 | * Or make a motivated request to support to register with your personal email. | ||
| 39 | |||
| 40 | ==== __**Case 2.2:**__ User has an institutional email ==== | ||
| 41 | |||
| 42 | You will be able to register in the Collaboratory 2, you will have 2 accounts created and 2 verification emails, one for the Collaboratory 2 at [[https:~~/~~/wiki.ebrains.eu/>>url:https://wiki.ebrains.eu/]], and the very same account for Collaboratory 1 at [[https:~~/~~/collab.humanbrainproject.eu/>>url:https://collab.humanbrainproject.eu/#/collab/]] | ||
| 43 | |||
| 44 | === Collaboratory 1 is deprecated === | ||
| 45 | |||
| 46 | Avoid creating new content in Collaboratory 1; it is deprecated. New collabs, files and notebooks should be added to Collaboratory 2 at [[https:~~/~~/wiki.ebrains.eu/>>url:https://wiki.ebrains.eu/]]. New services should request user authentication from Collaboratory 2 as well. | ||
| 47 | |||
| 48 | Plans are to assist collab administrators to migrate content from Collaboratory 1 to Collaboratory 2, and to shut off Collaboratory 1 by __**September 2021**__. | ||
| 49 | |||
| 50 |