Skip to content

Commit 4fad0d1

Browse files
committed
edit description
1 parent ecc921d commit 4fad0d1

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/vendor/licenses-about.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,19 @@ The Replicated Vendor Portal also allows vendors to create and manage customer r
1212

1313
Vendors can use these licensing features to enforce entitlements such as license expiration dates, and to track and report on software usage for the prupose of surfacing insights to both internal teams and customers.
1414

15-
The following diagram shows an overview of licensing with the Replicated Platform:
15+
The following diagram provides an overview of licensing with the Replicated Platform:
1616

1717
![App instance communicates with the Replicated licensing server](/images/licensing-overview.png)
1818

1919
[View a larger version of this image](/images/licensing-overview.png)
2020

21-
As shown in the diagram above, the Replicated license and update server retrieves customer details and license entitlements from the customer records that are managed by vendors in the Vendor Portal.
21+
As shown in the diagram above, the Replicated license and update server manages and distributes customer license information. The license server retrieves this license information from customer records managed by vendors in the Vendor Portal.
2222

23-
The license server is identified with a CNAME record where it can be accessed from end customer environments. When running alongside an application in a customer environment, the Replicated SDK retrieves up-to-date customer license information from the license server during runtime. The in-cluster SDK API `/license/` endpoints can be used to retrieve customer license details, allowing vendors to programmatically enforce and report on license agreements.
23+
During installation or upgrade, the license server provides the customer's license ID, which is used to authenticate with the Replicated Proxy Registry. In this way, the customer's license is used to securely grant proxy access to images in the vendor's external registry.
2424

25-
Additionally, during installation or upgrade, the Replicated Proxy Registry uses the customer's license ID to grant proxy access to images in the vendor's external registry.
25+
The license server is identified with a CNAME record where it can be accessed from end customer environments. When running alongside an application in a customer environment, the Replicated SDK retrieves up-to-date customer license information from the license server during runtime. The in-cluster SDK API `/license/` endpoints can be used to get customer license information on-demand, allowing vendors to programmatically enforce and report on license agreements.
2626

27-
Vendors can also integrate internal Customer Relationship Management (CRM) tools such as Salesforce with the Replicated Platform so that any changes to a customer's entitlements are automatically reflected in the customer records in the Vendor Portal.
27+
Vendors can also integrate internal Customer Relationship Management (CRM) tools such as Salesforce with the Replicated Platform so that any changes to a customer's entitlements are automatically reflected in the Vendor Portal. This ensures that updates to license agreements are reflected in the customer environment in real time.
2828

2929
## About Customers
3030

0 commit comments

Comments
 (0)