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
Copy file name to clipboardExpand all lines: docs/source/UserGuide/GettingStarted/GettingUserIdentity/index.rst
+32-2Lines changed: 32 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,33 @@ 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
+
.. versionadded:: 8.0
58
+
added the possibility to generate proxy with new `dirac-login` command, use *--help* switch for more information. E.g.: dirac-login <user_group>
59
+
60
+
Token authorization
61
+
-------------------
62
+
63
+
Starting with the 8.0 version of DIRAC, it is possible to authorize users through third party Identity Providers (IdP),
64
+
such as `EGI Checkin <https://www.egi.eu/services/check-in/>`_ or `WLCG IAM <https://indigo-iam.github.io/v/current/>`_.
65
+
You do not need a certificate for this in a terminal, but you must be registered in one of the supported IdP. The registration process is different for each IdP.
66
+
67
+
Once your account is created, you will be able to register with DIRAC Authorization Server using *--use-diracas* switch of the `dirac-login` command::
68
+
69
+
dirac-login <user_group> --use-diracas
70
+
71
+
You can request to return the access token instead of a proxy using *--token* key::
72
+
73
+
dirac-login <user_group> --token
74
+
75
+
But since not all services currently support tokens, you can get a proxy if you use the *--proxy* key::
76
+
77
+
dirac-login <user_group> --proxy --use-diracas
78
+
79
+
.. note:: if you want to get a proxy after logging in to DIRAC Authorization Server you must first put it in DIRAC, see "Proxy initialization".
80
+
81
+
If you need to end the work session in this way to remove the received access token and related information, then use the following::
0 commit comments