You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add comments and code documentation about token usage
add more comments and code docs
fix Auth to AuthDB
add docs and comments to TokenDB
Rebased to get pre-commit changes using
* gh pr checkout 5397
* git rebase 67f5059
* pre-commit run --all-files
* black src/DIRAC/ProductionSystem/DB/ProductionDB.py src/DIRAC/TransformationSystem/DB/TransformationDB.py
* git commit --no-edit -c 75afcca
* git rebase upstream/integration
Copy file name to clipboardExpand all lines: docs/source/UserGuide/GettingStarted/GettingUserIdentity/index.rst
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ The user will be prompted for the password used while exporting the certificate
19
19
to be used with the user's private key. Do not forget it !
20
20
21
21
Registration with DIRAC
22
-
-------------------------
22
+
-----------------------
23
23
24
24
Users are always working in the Grid as members of some User Community. Therefore, every user must be registered
25
25
with the Community DIRAC instance. You should ask the DIRAC administrators to do that, the procedure can
@@ -30,7 +30,7 @@ determines the user rights for various Grid operations. Each DIRAC installation
30
30
group to which the users are attributed when the group is not explicitly specified.
31
31
32
32
Proxy initialization
33
-
-----------------------
33
+
--------------------
34
34
35
35
Users authenticate with DIRAC services, and therefore with the Grid services that DIRAC expose via "proxies",
36
36
which you can regard as a product of personal certificates.
@@ -53,3 +53,20 @@ If another non-default user group is needed, the command becomes::
53
53
$ dirac-proxy-init -g <user_group>
54
54
55
55
where ``user_group`` is the desired DIRAC group name for which the user is entitled.
56
+
57
+
Token authorization
58
+
-------------------
59
+
60
+
Starting with the 8.0 version of DIRAC, it is possible to authorize users through third party Identity Providers (IdP),
61
+
such as EGI Checkin [https://www.egi.eu/services/check-in/] or WLCG IAM (https://indico.cern.ch/event/739896/contributions/3497694/attachments/1905332/3146590/IAM-WLCG-AuthZ-Fermilab-10092019.pdf).
62
+
To do this, you do not need to have a certificate if you use a terminal, the main thing is that you must be registered in one of the supported IdP. The registration process is different for each IdP.
63
+
64
+
Once your account is created, you will be able to register with DIRAC using the `dirac-login` command that will return tokens that will be used to access the services::
65
+
66
+
dirac-login -g <user_group>
67
+
68
+
But since not all services currently support tokens, you can get a proxy if you use the *--proxy* key::
69
+
70
+
dirac-login -g <user_group> --proxy
71
+
72
+
Note that to get a proxy you must first put it in DIRAC, see "Proxy initialization".
0 commit comments