Changes for page User documentation

Last modified by alexisdurieux on 2022/01/27 15:00
From version 4.1
edited by alexisdurieux
on 2022/01/27 14:42
Change comment: There is no comment for this version
To version 6.1
edited by alexisdurieux
on 2022/01/27 14:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,8 +17,6 @@
17 17  
18 18  Why does each service provider need a Fenix service account? The reason is that the Principal Investigator who gets the Fenix service account is legally responsible for the jobs being run on the supercomputers and for not enabling the end-user to run unintended executables.
19 19  
20 -[[image:Collabs.ebrains-unicore-job-proxy.User documentation.WebHome@ebrains-job-proxy-Job sequence.png]]
21 -
22 22  == Use case ==
23 23  
24 24  1. Bob wants to do use an EBRAINS Application that requires supercomputing.
... ... @@ -116,13 +116,13 @@
116 116  
117 117  Your application needs an EBRAINS IAM service account. You should contact EBRAINS __support__ to create it. You will need to provide a username and an email address which is not linked to another EBRAINS account. The mapping between the EBRAINS service account and the Fenix service account is done automatically based on the linked email addresses which need to be identical.
118 118  
119 -Your application needs an EBRAINS IAM OIDC client. See the __instructions__.
117 +Your application needs an EBRAINS IAM OIDC client. See the [[__instructions__>>https://wiki.ebrains.eu/bin/view/Collabs/the-collaboratory/Documentation%20IAM/FAQ/OIDC%20Clients%20explained/1.%20Registering%20an%20OIDC%20client/#HCreatingyourOpenIDConnectclient]].
120 120  
121 -Your application needs a Fenix project and a Fenix service account. See the __instructions__ to get a project. Then the Principal Investigator in your lab can request a Fenix service account via EBRAINS __support__.
119 +Your application needs a Fenix project and a Fenix service account. See the [[__instructions__>>https://fenix-ri.eu/access]] to get a project. Then the Principal Investigator in your lab can request a Fenix service account via EBRAINS [[__support__>>https://ebrains.eu/support/]].
122 122  
123 -Then in your app, you should retrieve the access token linked to your service account user. This requires the OIDC client ID, client Secret, EBRAINS service account's username and password. See the __instructions__.
121 +Then in your app, you should retrieve the access token linked to your service account user. This requires the OIDC client ID, client Secret, EBRAINS service account's username and password. See the [[__instructions__>>https://wiki.ebrains.eu/bin/view/Collabs/the-collaboratory/Documentation%20IAM/FAQ/OIDC%20Clients%20explained/1.%20Registering%20an%20OIDC%20client/#HFetchingyourdeveloperaccesstoken]].
124 124  
125 -When requesting a job on behalf of an end user, your app gives this access token in the field "**user_info**" of the payload alongside the job request. Note that the access token expires (typically after one week), so your application should generate a new token. See the __instructions__.
123 +When requesting a job on behalf of an end-user, your app gives this access token in the field "**user_info**" of the payload alongside the job request. Note that the access token expires (typically after one week), so your application should generate a new token.
126 126  
127 127  
128 128  __Example__: