Adding Users and Groups
Users logged in TIBCO Developer Hub have an identity that can be used to determine their ownership over any entity. A group or a user can own multiple software components. Users can be a part of a group or multiple groups, depends on how a software component is structured inside an organization. See Backstage Documentation to learn more about adding users and groups.
Linking a Control Plane User with Developer Hub
If a control plane user signs in to TIBCO Developer Hub, by default, a user identity is created for the user using the first part of their used email address. For example, if the email id of the user is example@domain.com
. Then, the user identity is created with the first part (example
) of their email before ‘@’
).
If a user entity exists in the software catalog with the same name, linking the user entity with other software catalog entities works fine. Otherwise, create a user entity in the software catalog with the same name. You can create the users by using the following two methods.
Below are the two ways to create users and groups.
Manually Registering Users and Groups
If a control plane user has an email id example@domain.com
. A name
of that user should be the first part of their email before ‘@’
. The name
is referenced as example
. Now, create a YAML config file in your GitHub repository by following the below structure.
apiVersion: backstage.io/v1alpha1 kind: User metadata: namespace: default name: example spec: profile: displayName: Fname Lname email: example@domain.com
After creating, use this GitHub YAML file link and follow the Registering an Existing Component steps to register users and groups manually.
Adding Users and Groups from GitHub Organization
username
of the user must be the same as the first half of the email as described in the Adding Users and Groups to create the required user entity in the software catalog.
After adding users (people) and groups (teams) to your GitHub organization, link your GitHub org with the developer hub instance to display all users and groups in the catalog.
Use the below configuration while provisioning, replace the org name with your-github-org-name
and provide a custom-provider-id
.