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: pages/manage_and_operate/iam/identities-management/guide.en-asia.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Presentation of identities that can interact within an OVHcloud account"
3
3
excerpt: "Discover the different types of identities that allow you to interact with an OVHcloud product"
4
-
updated: 2024-03-05
4
+
updated: 2024-10-21
5
5
---
6
6
7
7
## Objective
@@ -22,7 +22,7 @@ There are several types of identities that can interact with OVHcloud products:
22
22
23
23
### OVHcloud account
24
24
25
-
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address.
25
+
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address or NIC handle (e.g. xx1111-ovh).
26
26
27
27
This identity acts as a root account and cannot have its rights restricted, regardless of the access policies implemented.
28
28
@@ -40,6 +40,8 @@ In order for an application based on a token linked to a local user to use an OV
40
40
41
41
Local users can also be referred to as *sub-users* in the documentation.
42
42
43
+
We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
44
+
43
45
### Service accounts
44
46
45
47
Service accounts are identities associated with your OVHcloud account. These accounts are designed for **machine interactions** with OVHcloud products, as they are based on client/token authentication, and access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
@@ -48,19 +50,27 @@ The creation of service accounts is covered in a [dedicated documentation](/page
48
50
49
51
A service account can then be used for [login on OVHcloud APIs](/pages/account_and_service_management/account_information/authenticate-api-with-service-account) as well as on third-party APIs such as those exposed by [OpenStack](/pages/manage_and_operate/iam/authenticate-api-openstack-with-service-account).
50
52
51
-
Logging in with service accounts is not yet supported on SDKs and Terraform provider.
52
-
53
53
### Federated users
54
54
55
55
These are user accounts from an [identity federation](/products/manage-operate-user-federation). These users come from a third-party directory, and are therefore not managed directly by OVHcloud. Their access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
56
56
57
57
Federated users are represented by user groups in rights management.
58
58
59
+
We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
60
+
59
61
### User groups
60
62
61
63
The different identities can be associated in user groups to make them easier to manipulate.
62
64
Configuring user groups is covered in the [local users management documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
63
65
66
+
### Users of OVHcloud products
67
+
68
+
Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
69
+
Those users are independant from the OVHcloud account and are managed directly through the products concerned.
70
+
71
+
For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
72
+
On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
73
+
64
74
## Go further
65
75
66
76
Identity management can be automated via the [OVHcloud APIs](/pages/manage_and_operate/api/first-steps) or via the [provider Terraform OVHcloud](/pages/manage_and_operate/terraform/terraform-at-ovhcloud).
Copy file name to clipboardExpand all lines: pages/manage_and_operate/iam/identities-management/guide.en-au.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Presentation of identities that can interact within an OVHcloud account"
3
3
excerpt: "Discover the different types of identities that allow you to interact with an OVHcloud product"
4
-
updated: 2024-03-05
4
+
updated: 2024-10-21
5
5
---
6
6
7
7
## Objective
@@ -22,7 +22,7 @@ There are several types of identities that can interact with OVHcloud products:
22
22
23
23
### OVHcloud account
24
24
25
-
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address.
25
+
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address or NIC handle (e.g. xx1111-ovh).
26
26
27
27
This identity acts as a root account and cannot have its rights restricted, regardless of the access policies implemented.
28
28
@@ -40,6 +40,8 @@ In order for an application based on a token linked to a local user to use an OV
40
40
41
41
Local users can also be referred to as *sub-users* in the documentation.
42
42
43
+
We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
44
+
43
45
### Service accounts
44
46
45
47
Service accounts are identities associated with your OVHcloud account. These accounts are designed for **machine interactions** with OVHcloud products, as they are based on client/token authentication, and access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
@@ -48,19 +50,27 @@ The creation of service accounts is covered in a [dedicated documentation](/page
48
50
49
51
A service account can then be used for [login on OVHcloud APIs](/pages/account_and_service_management/account_information/authenticate-api-with-service-account) as well as on third-party APIs such as those exposed by [OpenStack](/pages/manage_and_operate/iam/authenticate-api-openstack-with-service-account).
50
52
51
-
Logging in with service accounts is not yet supported on SDKs and Terraform provider.
52
-
53
53
### Federated users
54
54
55
55
These are user accounts from an [identity federation](/products/manage-operate-user-federation). These users come from a third-party directory, and are therefore not managed directly by OVHcloud. Their access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
56
56
57
57
Federated users are represented by user groups in rights management.
58
58
59
+
We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
60
+
59
61
### User groups
60
62
61
63
The different identities can be associated in user groups to make them easier to manipulate.
62
64
Configuring user groups is covered in the [local users management documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
63
65
66
+
### Users of OVHcloud products
67
+
68
+
Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
69
+
Those users are independant from the OVHcloud account and are managed directly through the products concerned.
70
+
71
+
For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
72
+
On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
73
+
64
74
## Go further
65
75
66
76
Identity management can be automated via the [OVHcloud APIs](/pages/manage_and_operate/api/first-steps) or via the [provider Terraform OVHcloud](/pages/manage_and_operate/terraform/terraform-at-ovhcloud).
Copy file name to clipboardExpand all lines: pages/manage_and_operate/iam/identities-management/guide.en-ca.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Presentation of identities that can interact within an OVHcloud account"
3
3
excerpt: "Discover the different types of identities that allow you to interact with an OVHcloud product"
4
-
updated: 2024-03-05
4
+
updated: 2024-10-21
5
5
---
6
6
7
7
## Objective
@@ -22,7 +22,7 @@ There are several types of identities that can interact with OVHcloud products:
22
22
23
23
### OVHcloud account
24
24
25
-
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address.
25
+
This is the primary identity used to log in to the OVHcloud Control Panel. You use the OVHcloud account when you log in to the OVHcloud Control Panel with your email address or NIC handle (e.g. xx1111-ovh).
26
26
27
27
This identity acts as a root account and cannot have its rights restricted, regardless of the access policies implemented.
28
28
@@ -40,6 +40,8 @@ In order for an application based on a token linked to a local user to use an OV
40
40
41
41
Local users can also be referred to as *sub-users* in the documentation.
42
42
43
+
We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
44
+
43
45
### Service accounts
44
46
45
47
Service accounts are identities associated with your OVHcloud account. These accounts are designed for **machine interactions** with OVHcloud products, as they are based on client/token authentication, and access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
@@ -48,19 +50,27 @@ The creation of service accounts is covered in a [dedicated documentation](/page
48
50
49
51
A service account can then be used for [login on OVHcloud APIs](/pages/account_and_service_management/account_information/authenticate-api-with-service-account) as well as on third-party APIs such as those exposed by [OpenStack](/pages/manage_and_operate/iam/authenticate-api-openstack-with-service-account).
50
52
51
-
Logging in with service accounts is not yet supported on SDKs and Terraform provider.
52
-
53
53
### Federated users
54
54
55
55
These are user accounts from an [identity federation](/products/manage-operate-user-federation). These users come from a third-party directory, and are therefore not managed directly by OVHcloud. Their access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
56
56
57
57
Federated users are represented by user groups in rights management.
58
58
59
+
We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
60
+
59
61
### User groups
60
62
61
63
The different identities can be associated in user groups to make them easier to manipulate.
62
64
Configuring user groups is covered in the [local users management documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
63
65
66
+
### Users of OVHcloud products
67
+
68
+
Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
69
+
Those users are independant from the OVHcloud account and are managed directly through the products concerned.
70
+
71
+
For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
72
+
On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
73
+
64
74
## Go further
65
75
66
76
Identity management can be automated via the [OVHcloud APIs](/pages/manage_and_operate/api/first-steps) or via the [provider Terraform OVHcloud](/pages/manage_and_operate/terraform/terraform-at-ovhcloud).
Copy file name to clipboardExpand all lines: pages/manage_and_operate/iam/identities-management/guide.en-gb.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Presentation of identities that can interact within an OVHcloud account"
3
3
excerpt: "Discover the different types of identities that allow you to interact with an OVHcloud product"
4
-
updated: 2024-03-05
4
+
updated: 2024-10-21
5
5
---
6
6
7
7
## Objective
@@ -10,7 +10,7 @@ The purpose of this guide is to present the different types of identities that c
10
10
11
11
## Requirements
12
12
13
-
- An [OVHcloud customer account](/pages/account_and_service_management/account_information/ovhcloud-account-creation)
13
+
- An [OVHcloud customer account](/pages/account_and_service_management/account_information/ovhcloud-account-creation).
14
14
15
15
## Instructions
16
16
@@ -40,6 +40,8 @@ In order for an application based on a token linked to a local user to use an OV
40
40
41
41
Local users can also be referred to as *sub-users* in the documentation.
42
42
43
+
We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
44
+
43
45
### Service accounts
44
46
45
47
Service accounts are identities associated with your OVHcloud account. These accounts are designed for **machine interactions** with OVHcloud products, as they are based on client/token authentication, and access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
@@ -48,19 +50,27 @@ The creation of service accounts is covered in a [dedicated documentation](/page
48
50
49
51
A service account can then be used for [login on OVHcloud APIs](/pages/account_and_service_management/account_information/authenticate-api-with-service-account) as well as on third-party APIs such as those exposed by [OpenStack](/pages/manage_and_operate/iam/authenticate-api-openstack-with-service-account).
50
52
51
-
Logging in with service accounts is not yet supported on SDKs and Terraform provider.
52
-
53
53
### Federated users
54
54
55
55
These are user accounts from an [identity federation](/products/manage-operate-user-federation). These users come from a third-party directory, and are therefore not managed directly by OVHcloud. Their access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
56
56
57
57
Federated users are represented by user groups in rights management.
58
58
59
+
We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
60
+
59
61
### User groups
60
62
61
63
The different identities can be associated in user groups to make them easier to manipulate.
62
64
Configuring user groups is covered in the [local users management documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
63
65
66
+
### Users of OVHcloud products
67
+
68
+
Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
69
+
Those users are independant from the OVHcloud account and are managed directly through the products concerned.
70
+
71
+
For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
72
+
On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
73
+
64
74
## Go further
65
75
66
76
Identity management can be automated via the [OVHcloud APIs](/pages/manage_and_operate/api/first-steps) or via the [provider Terraform OVHcloud](/pages/manage_and_operate/terraform/terraform-at-ovhcloud).
Copy file name to clipboardExpand all lines: pages/manage_and_operate/iam/identities-management/guide.en-ie.md
+13-3
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Presentation of identities that can interact within an OVHcloud account"
3
3
excerpt: "Discover the different types of identities that allow you to interact with an OVHcloud product"
4
-
updated: 2024-03-05
4
+
updated: 2024-10-21
5
5
---
6
6
7
7
## Objective
@@ -40,6 +40,8 @@ In order for an application based on a token linked to a local user to use an OV
40
40
41
41
Local users can also be referred to as *sub-users* in the documentation.
42
42
43
+
We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
44
+
43
45
### Service accounts
44
46
45
47
Service accounts are identities associated with your OVHcloud account. These accounts are designed for **machine interactions** with OVHcloud products, as they are based on client/token authentication, and access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
@@ -48,19 +50,27 @@ The creation of service accounts is covered in a [dedicated documentation](/page
48
50
49
51
A service account can then be used for [login on OVHcloud APIs](/pages/account_and_service_management/account_information/authenticate-api-with-service-account) as well as on third-party APIs such as those exposed by [OpenStack](/pages/manage_and_operate/iam/authenticate-api-openstack-with-service-account).
50
52
51
-
Logging in with service accounts is not yet supported on SDKs and Terraform provider.
52
-
53
53
### Federated users
54
54
55
55
These are user accounts from an [identity federation](/products/manage-operate-user-federation). These users come from a third-party directory, and are therefore not managed directly by OVHcloud. Their access rights depend on the [IAM policies](/pages/account_and_service_management/account_information/iam-policy-ui) implemented.
56
56
57
57
Federated users are represented by user groups in rights management.
58
58
59
+
We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
60
+
59
61
### User groups
60
62
61
63
The different identities can be associated in user groups to make them easier to manipulate.
62
64
Configuring user groups is covered in the [local users management documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
63
65
66
+
### Users of OVHcloud products
67
+
68
+
Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
69
+
Those users are independant from the OVHcloud account and are managed directly through the products concerned.
70
+
71
+
For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
72
+
On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
73
+
64
74
## Go further
65
75
66
76
Identity management can be automated via the [OVHcloud APIs](/pages/manage_and_operate/api/first-steps) or via the [provider Terraform OVHcloud](/pages/manage_and_operate/terraform/terraform-at-ovhcloud).
0 commit comments