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
Any `:` within the metadata values will be replaced with `%3A` in the subject claim.
151
+
152
+
You can configure a subject that includes metadata containing colons. In this example, the workflow run must have originated from a job that has an environment named `Production:V1`, in a repository named `octo-repo` that is owned by the `octo-org` organization:
To configure the subject in your cloud provider's trust relationship, you must add the subject string to its trust configuration. The following examples demonstrate how various cloud providers can accept the same `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` subject in different ways:
@@ -52,7 +53,7 @@ Administrators for the enterprise account can:
52
53
53
54
## What if I use multiple deployment options?
54
55
55
-
If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you'll have an enterprise account for each.
56
+
If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you'll have **an enterprise account for each.**
56
57
57
58
For the most part, you will manage each enterprise account separately. For example, you will configure the policies and settings for your {% data variables.product.prodname_ghe_server %} instance using the enterprise account on {% data variables.product.prodname_ghe_server %}.
intro: 'Learn the fundamental concepts that you''ll need to understand {% data variables.location.product_location %}, including fundamentals, identity and access management, security and compliance, and best practices.'
Copy file name to clipboardExpand all lines: content/admin/concepts/enterprise-fundamentals/roles-in-an-enterprise.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,21 @@
1
1
---
2
-
title: About roles in an enterprise
2
+
title: Roles in an enterprise
3
3
intro: 'Learn how roles allow you to control people''s access to your enterprise''s settings and resources.'
4
4
versions:
5
5
ghec: '*'
6
6
ghes: '*'
7
-
shortTitle: About roles
8
-
type: overview
7
+
shortTitle: Roles
9
8
topics:
10
9
- Enterprise
11
10
- Fundamentals
11
+
redirect_from:
12
+
- /admin/overview/about-roles
13
+
contentType: concepts
12
14
---
13
15
14
16
## What are roles?
15
17
16
-
A role is a set of permissions that you can assign to individuals or teams. A permission is the ability to perform a specific action, such as changing billing settings.
18
+
A role is a **set of permissions** that you can assign to individuals or teams. A permission is the ability to perform a specific action, such as changing billing settings.
17
19
18
20
A user in an enterprise has a role for both the enterprise account itself and for each individual organization in the enterprise.
19
21
@@ -35,7 +37,7 @@ Enterprise roles are assigned when a user is invited to the enterprise (personal
35
37
36
38
Organization administrators can grant organization roles and create custom organization roles, but can't affect roles at the enterprise level.
37
39
38
-
## Next steps
40
+
## Further reading
39
41
40
42
Review the predefined roles and fine-grained permissions available with custom organization roles, and plan out what roles will be required for your teams to do their jobs on {% data variables.product.github %}.
Copy file name to clipboardExpand all lines: content/admin/concepts/identity-and-access-management/enterprise-managed-users.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: 'About {% data variables.product.prodname_emus %}'
3
-
shortTitle: About managed users
2
+
title: About {% data variables.product.prodname_emus %}
3
+
shortTitle: Enterprise Managed Users
4
4
intro: 'Learn how your enterprise can manage the lifecycle and authentication of users on {% data variables.product.prodname_dotcom %} from your identity provider (IdP).'
With {% data variables.product.prodname_emus %}, you manage the lifecycle and authentication of your users on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} from an external identity management system, or IdP:
31
+
## What are Enterprise Managed Users in {% data variables.product.github %}?
32
+
33
+
With {% data variables.product.prodname_emus %}, you manage the lifecycle and authentication of your users on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %} **from an external identity management system, or IdP**:
31
34
32
35
* Your IdP **provisions new user accounts** on {% data variables.product.prodname_dotcom %}, with access to your enterprise.
33
36
* Users must **authenticate on your IdP** to access your enterprise's resources on {% data variables.product.prodname_dotcom %}.
@@ -37,11 +40,11 @@ With {% data variables.product.prodname_emus %}, you manage the lifecycle and au
37
40
38
41
> [!NOTE] {% data variables.product.prodname_emus %} is not the best solution for every customer. To determine whether it's right for your enterprise, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud).
39
42
40
-
## Identity management systems
43
+
## How does EMUs integrate with identity management systems?
41
44
42
45
{% data reusables.enterprise_user_management.emu-paved-path-iam-integrations %}
43
46
44
-
### Partner identity providers
47
+
### What are partner identity providers?
45
48
46
49
Partner IdPs provide authentication using SAML or OIDC, and provide provisioning with System for Cross-domain Identity Management (SCIM).
47
50
@@ -57,7 +60,7 @@ Partner IdPs provide authentication using SAML or OIDC, and provide provisioning
57
60
58
61
When you use a single partner IdP for both authentication and provisioning, {% data variables.product.company_short %} provides support for the application on the partner IdP and the IdP's integration with {% data variables.product.prodname_dotcom %}.
59
62
60
-
### Other identity management systems
63
+
### Can I use identity management systems other than the supported partners?
61
64
62
65
If you cannot use a single partner IdP for both authentication and provisioning, you can use another identity management system or combination of systems. The system must:
63
66
@@ -67,7 +70,7 @@ If you cannot use a single partner IdP for both authentication and provisioning,
67
70
68
71
{% data reusables.emus.mixed-systems-note %}
69
72
70
-
## Usernames and profile information
73
+
## How are usernames and profile information managed for EMUs?
71
74
72
75
{% data variables.product.prodname_dotcom %} automatically creates a username for each developer by normalizing an identifier provided by your IdP. If the unique parts of the identifier are removed during normalization, a conflict may occur. See [AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems).
73
76
@@ -76,13 +79,13 @@ The profile name and email address of a {% data variables.enterprise.prodname_ma
76
79
* The IdP can only provide one email address.
77
80
* Changing a user's email address in your IdP will unlink the user from the contribution history associated with the old email address.
78
81
79
-
## Managing roles and access
82
+
## How are roles and access managed for EMUs?
80
83
81
84
In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} a **role in your enterprise**, such as member, owner, or guest collaborator. See [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
82
85
83
86
Organization memberships (and repository access) can be managed manually, or you can **update memberships automatically using IdP groups**. See [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups).
84
87
85
-
## Authentication for {% data variables.enterprise.prodname_managed_users %}
88
+
## How do {% data variables.enterprise.prodname_managed_users %} authenticate to {% data variables.product.prodname_dotcom %}?
86
89
87
90
The locations where {% data variables.enterprise.prodname_managed_users %} can authenticate to {% data variables.product.prodname_dotcom %} depends on how you configure authentication (SAML or OIDC). See [AUTOTITLE](/authentication/authenticating-with-single-sign-on/authenticating-with-a-managed-user-account).
intro: 'Learn the concepts around identity and access management (IAM) for {% data variables.location.product_location %}, including authentication, authorization, {% ifversion ghec %}Enterprise Managed Users, {% endif %}and user management.'
0 commit comments