This topic contains important information about this and previous releases of the AD RMS SDK 2.1.
The File API components of SDK has been extended and offers the following features:
- Identifies which protector to use.
- Provides RMS protection at the granularity level of a file.
Functions added in this release:
Note Further supporting data types and structures, not listed here, have been added for the File API extensions. All topics that have been updated for this release are marked as preliminary and subject to change.
- File API memory usage, especially for large PFiles has been improved significantly.
- Content ID is now writable via the property IPC_LI_CONTENT_ID. For more information, see License property types.
- Production manifest requirement - When your RMS enabled application/service is being run in server mode, we will not require a manifest anymore. For more information, see Application types.
- Documentation updates
- Reorganized - How-to use to clarify the order of steps for environment setup and application testing.
- Testing best practice - guidance added for use of on-premise server before testing with Azure RMS. For more information, see Enable your service application to work with cloud based RMS.
- Native support for all file types
Native support can be added for any file type (extension) with this release of Active Directory Rights Management Services SDK 2.1. For instance, for any extension <ext> (non-office and pdf), *.p<ext> will be used if the admin configuration for that extension is "NATIVE".
For more information on supported file types, see File API configuration.
- File API integration
The Active Directory Rights Management Services File API , with the addition of File API, provides the following benefits and capabilities.
- You can protect confidential data in an automated way without having to know the details of the Information Rights Management (IRM) implementation used by various file formats.
- Microsoft Office files, Portable Document Format (PDF) files, and selected other file types can be protected using native protection. For a complete list of file types that can be protected with native protection, see File API configuration.
- All files, except system files and Office files can be protected using AD RMS Protected File format (PFile).
The File API requires that the Active Directory Rights Management Services Client 2.1 be installed on the client computer and that the computer have connectivity to an AD RMS server. For more information on AD RMS server, AD RMS client, and their functionality, see the TechNet content for IT Pro documentation for AD RMS.
Issue: When creating a license from scratch, ownership rights must be granted explicitly.
Solution: Your application must explicitly add Owner rights to the license owner when creating a license from scratch using IpcCreateLicenseFromScratch. For more information, see Add explicit owner rights.
Issue: When building for multiple architectures, you must use this guidance.
Solution: If you want to use the Ipcsecproc*isv.dll for a different architecture (for example, you have installed the 64-bit SDK on a 64-bit computer but now want to deploy on a 32-bit computer that requires Ipcsecproc*isv.dll), you must install the 32-bit SDK on a different computer and copy the Ipcsecproc*isv.dll files to there from the %PROGRAMFILES%\Microsoft Information Protection And Control folder (the default location or wherever you chose to install the SDK).
Q: How does the default language behavior work with functions that take an LCID parameter?
A: Use 0 for the default locale. In this case, AD RMS Client 2.1 looks up names and descriptions in the following sequence and retrieves the first available one:
- 1 - User preferred LCID.
- 2 - System locale LCID.
- 3 - The first available language specified in the Rights Management Server (RMS) template.
- Add explicit owner rights
- File API configuration