Developer Kits

The protectedpdf server can be extended and customized to integrate with your existing systems. Vitrium's developer kits and the accompanying samples describe how you can greatly enhance the end user experience and meet a variety of business needs.

All of the kits have been secured using the protectedpdf technology. To gain full access to a document, simply fill out and submit the form on its cover page. Vitrium values your privacy and any information provided when unlocking the kits will never be shared with third parties.

External Identity Provider Kit (EIP)

For credential-based documents, the protectedpdf server includes a built-in Identity Provider. The built-in Identity Provider uses email and password pairs as credentials. If you wish to use credentials other than email and password pairs or you wish to maintain your customer information in a system separate from the protectedpdf server (such as a shopping cart), you can implement an EIP. When using an EIP, you may customize credentials to your needs e.g. username and password pairs, serial numbers or even IP address ranges.

EIP Documentation External Identity Provider Kit
EIP Sample Code EIP C#

Software Integration Kit (SDK)

The Software Integration Kit describes in detail how you can integrate and extend your publishing pipeline to automatically generate protectedpdf documents. This will allow you to seamlessly add Rights Management to PDF documents and control access to documents, based on any criteria you choose.

SDK Documentation Software Integration Kit
SDK Sample Code SDK C#, SDK VB, SDK Java

Template Developers Kit (TDK)

This document describes in detail how to create custom cover pages (or templates) in order to brand your documents.

TDK Documentation Template Developers Kit
TDK Samples TDK Samples

External Forms Server Kit (EFS)

The protectedpdf server can be used to create protectedpdf documents with forms. When the reader opens these documents they will be presented with a form which queries them for specific information i.e. name, company, phone number and email address. The reader must complete this form before being granted access to protected content. The EFS receives the information entered by a reader into the document form. This information can be sent to an internal system, such as a CRM database.

EFS Documentation External Forms Server Kit
EFS Sample Code EFS C#