Abstract:
A digital content distribution framework is provided. According to one embodiment, a digital content distribution system, such as a software distribution system, includes a credentialing authority, an access control component, and a digital content distribution system interface for each participant in the system. The credentialing authority component is configured to receive encryption keys associated with the participants and assign each of the participants an identity certificate for use during subsequent interactions with components of the digital content distribution system. The access control component is configured to maintain information regarding access rights of the participants to digital content accessible via the digital content distribution system. The digital content distribution system interfaces are capable of being customized for the corresponding participant and are configured to coordinate interactions among the corresponding participant and the components of the digital content distribution system according to predetermined business processes associated with the corresponding participant.
Abstract:
A digital content distribution framework is provided. According to one embodiment, a digital content distribution system, such as a software distribution system, includes a credentialing authority, an access control component, and a digital content distribution system interface for each participant in the system. The credentialing authority component is configured to receive encryption keys associated with the participants and assign each of the participants an identity certificate for use during subsequent interactions with components of the digital content distribution system. The access control component is configured to maintain information regarding access rights of the participants to digital content accessible via the digital content distribution system. The digital content distribution system interfaces are capable of being customized for the corresponding participant and are configured to coordinate interactions among the corresponding participant and the components of the digital content distribution system according to predetermined business processes associated with the corresponding participant.
Abstract:
Embodiments relate generally to ensuring version compliance for software products used within an enterprise. Generally, compliance is checked by comparing the number of actual uses of each product version to license information relating to product versions. An enterprise is compliant if use of a product version is covered by a license. License information and actual usage information are generally collected to allow for such a comparison. Information concerning license attributes such as downgrade coverage and/or license type may allow for a more accurate determination of the number of each product version ultimately available. Additionally, a rollup procedure may be used to apply updates to base licenses. Version compliance may be performed as a stand-alone feature, or it may be used in conjunction with an entitlement coordination framework to manage usage throughout the enterprise.
Abstract:
A computer readable media containing instructions for a processor to implement a plurality of steps comprising: accessing a time constraint for an entitlement, determining whether the time constraint has been satisfied, and responsive to the determination that the time constraint has been satisfied, modifying the entitlement, wherein the duration of the entitlement is less than the duration of the license for the digital content.
Abstract:
A computer readable media containing instructions for a processor to implement a plurality of steps comprising: accessing a time constraint for an entitlement, determining whether the time constraint has been satisfied, and responsive to the determination that the time constraint has been satisfied, modifying the entitlement, wherein the duration of the entitlement is less than the duration of the license for the digital content.
Abstract:
Embodiments relate generally to ensuring version compliance for software products used within an enterprise. Generally, compliance is checked by comparing the number of actual uses of each product version to license information relating to product versions. An enterprise is compliant if use of a product version is covered by a license. License information and actual usage information are generally collected to allow for such a comparison. Information concerning license attributes such as downgrade coverage and/or license type may allow for a more accurate determination of the number of each product version ultimately available. Additionally, a rollup procedure may be used to apply updates to base licenses. Version compliance may be performed as a stand-alone feature, or it may be used in conjunction with an entitlement coordination framework to manage usage throughout the enterprise.