Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
cloudappliance/licensekeys [2019_11_29 16:31] – jim | cloudappliance:licensekeys [2024_02_28 01:03] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Host Bindings in File Fabric | + | ==== Host Bindings in Access Anywhere |
- | == last updated on Nov. 28, 2019 == | + | == last updated on April 14, 2021 == |
- | SME introduced a new style of license keys in v1901 of the File Fabric. One of the most important features of these new style keys is that each key is bound to a particular | + | A new style of license keys were introduced |
Here is how it works: | Here is how it works: | ||
- | * Each key contains a list of zero or more fully qualified domain names (FQDNs), and a list of zero or more IP addresses. | + | * Each key contains a list of zero or more fully qualified domain names (FQDNs), and a list of zero or more IP addresses. |
- | | + | * If there are entries in the FQDN list then Access Anywhere |
- | * If there are entries in the IP address list then the File Fabric | + | * If there are entries in the IP address list then Access Anywhere |
- | Some customers who use CloudFTP create an FQDN specifically for use by FTP client programs, for example: ftp.myfilefabric.com. Before client programs can use the FTP FQDN, a license key in which the FTP FQDN appears on the FQDN list must be installed in the File Fabric. | + | Some customers who use CloudFTP create an FQDN specifically for use by FTP client programs, for example: ftp.myfilefabric.com. Before client programs can use the FTP FQDN, a license key in which the FTP FQDN appears on the FQDN list must be installed in Access Anywhere. |