You will frequently need to generate a new license key due to either user error or system error.
Self-managed licenses are managed in CustomersDot. Access to the application is managed through Okta, in order to request access please open an access request and refer that your role entitles you to access with this link.
An overview of the different licenses types can be seen in this handbook page (internal only).
The type of the License object associated to a subscription version can be identified by using the info below:
License type | Turn On Cloud Licensing |
---|---|
Cloud License | 'Yes' |
Offline License | 'Offline' |
Legacy License | 'No' or null |
To re-issue a license:
Duplicate license
button on the right (looks like the copy symbol).
Note: Only Legacy Licenses can be duplicated as of today.Customer
field.
Note: Changing the Customer
causes the inputs for name, email and company to be overriden on creation with the selected customer's information. This is a bug that will be addressed in https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3566.Notes
field, describe why you're issuing this license and add a link
to the Zendesk ticket or GitLab issue for the request if applicable.
Manually Generate Trial License
(for trials) or Manually Generate License
.Save
.The license should be emailed out immediately. Please note that a license should always be sent to the end user. Do not email the license to a Gitlab team member or a reseller. Note: If you want to send the license to a different email address use this handbook page instead.
When an existing license isn't available to duplicate, use the create new license section.
To create a new license, click Add new License
then follow the process listed below for creating a Legacy License or Offline Cloud License.
Note:
Legacy License
in the License type
drop down.Notes
field, describe why you're issuing this license and add a link
to the Zendesk ticket or GitLab issue for the request if applicable.
Manually Generate Trial License
(for trials) or Manually Generate License
.Save
.Currently the following fields are required for a Legacy License:
License type
Name
Company
Email
Users count
Plan code
Starts at
Expires at
Required to be filled by Support:
Customer
Zuora subscription ID
Notes
When creating an Offline License, the following has to be present beforehand:
Turn on seat reconciliation
field is present).Turn On Cloud Licensing
set to Offline
or No
).Offline Cloud
in the License type
drop down.Customer
field.
Note: This field is required for Offline Cloud Licenses.Notes
field, describe why you're issuing this license and add a link
to the Zendesk ticket or GitLab issue for the request if applicable.
Manually Generate Trial License
(for trials) or Manually Generate License
.Save
.Currently the following fields are required for an Offline Cloud License:
License type
Customer
Name
Company
Email
Zuora subscription ID
Users count
Plan code
Starts at
Expires at
Required to be filled by Support:
Notes
With Strict Cloud Licensing, Online Cloud Subscriptions only send out an activation code. A license will no longer be supplied. Hence, license creation for this type is not supported.