Summary
The binding elements for the trusted storage based licensing (for one's implementation) can be gathered from "<vendor>TrustedConfigIn.xml" file. This is a publisher side file, that can be located under platform Dir\publisher\<vendor_name>TrustedConfigIn.xml
It looks like this:
</TransactionKeyInfo>
<Server>
<Anchoring>
</Anchoring>
<Binding>
<Platform>
<Type>DEFAULT</Type>
</Platform>
</Binding>
</Server>
<Client>
<Anchoring>
</Anchoring>
<Binding>
<Platform>
<Type>DEFAULT</Type>
In regards of the Deal breaker scenarios for TS breakage, there is a detailed Table (A-24) explained in the "FlexNet Publisher Programming Reference for Trusted Storage–Based Licensing", under Appendix A.
The default for FLEXIBLE binding is to use all the built-in bindings that are available on an operating system. The list of those binding elements can be referred from the same document location (chapter/Appendix) as in my previous communication. However, users who are not using FlexNet Operations can specify the <Disable> or <Enable> element along with <HID> to identify explicitly which binding identities to use or not to use for a given operating system.
Also, FlexNet Publisher automatically uses the appropriate binding elements when running in a virtual environment, if they are available. Binding is to differentiate between physical and virtual environments and the legacy bind-to-VMID policy is deprecated. The binding elements are (for virtualization based environment):
- MAC address—used on physical environments is now used in virtual environments as well and is a deal breaker.
- UUID (universally unique ID)—A binding identity used to configure trusted storage on the virtual machine, previously the only binding identity used in virtual environments; this is now a deal breaker.
- Generation ID—A property of a virtual machine available in some environments. Where it is available it is used as a binding identity; it is a deal breaker.
A binding item is a deal breaker if/when it changes, trust should be lost regardless of the number of binding items that still match. Since all binding identities used in virtual environments are deal breakers, trust will always be lost if any of them changes.
Related Articles
Building of the Production FNP Licensing Toolkit for Trusted Storage may result in the error: Trusted config processing fa… 9Number of Views Best practices" document for Trusted Storage 6Number of Views FlexNet Embedded Error: 7000002c (Identity data has changed - trusted storage or anchor data cannot be decrypted) 9Number of Views Is Trusted Storage supported in a VMware environment? 5Number of Views Trusted Storage Keeps Breaking 30Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago