I know that most of you that frequent this blog are IT professionals and so familiarity with the developer experience in working with AD RMS might not be your primary focus, but when we on the Information Protection team rollout something that can really empower the AD RMS developers that you partner with to make a great solution that you can help be a part of bringing about, we want to make sure you are aware of it.
With the release a few months back of both the AD RMS Client 2.0 and the AD RMS SDK 2.0, we have made some real strides forward in simplifying the amount of code that is required to produce AD RMS-aware applications. Building on these recent developer enhancements, I’d like to give you a “heads up” about another cool thing that we have added for AD RMS developers, the RMS File API.
The File API is a new API that allows applications to easily protect and unprotect files in a single operation. With the file API, you pass the file to an API along with the policy you want applied and the API does the rest. It will identify the file’s format, and then protect the file appropriately. If it can’t find a suitable protector it will use the brand new Protected File format to encrypt the file and embed access controls so the file is protected in a generic format. It’s a much simpler and effective way to go.
So if you want to know more of the technical details, please check out our recent post on the AD RMS Developer’s Corner blog and be sure to let your developer friends who are interested in rights management know about this new API. It’s bound to save them time and coding.