Secure Content Provider Interfaces
.gif) |
This section describes the COM interfaces that make up a secure content provider implementation. The content-securing provider implements these interfaces. They are then acquired by the Windows Media Device Manager during operations that access content, and their methods are called to perform secured-content interactions.
A secure content provider implementation includes the following interfaces.
| Interface | Description |
| ISCPSecureAuthenticate | Handles authentication for Windows Media Device Manager. This is the primary interface of the secure content provider. |
| ISCPSecureAuthenticate2 | Extends ISCPSecureAuthenticate by providing a way to get a session object. |
| ISCPSecureExchange | Exchanges secured content and rights associated with content. |
| ISCPSecureExchange2 | Extends ISCPSecureExchange by providing a new version of TransferContainerData2 method which accepts a progress callback on which the secure content provider can send progress notifications for any of the steps it needs to carry out. |
| ISCPSecureExchange3 | Extends ISCPSecureExchange2 by providing a set of new methods for the device. |
| ISCPSecureQuery | Determines whether the secure content provider is responsible for the content. |
| ISCPSecureQuery2 | Extends ISCPSecureQuery through functionality that determines whether the secure content provider is responsible for the content, and if so, providing a URL for updating revoked components and determining which components have been revoked. |
| ISCPSecureQuery3 | Extends ISCPSecureQuery2 by providing a set of new methods for retrieving the rights and making decisions on a clear channel. |
| ISCPSession | Provides efficient common state management for multiple operations. |
See Also