Adobe Vendor ID

The Ultimate Solution for Seamless, Branded Content Authorization

Revolutionize your user experience, eliminate friction in eBook activation, and strengthen your digital ecosystem without relying on external Adobe IDs.

The Difference is in the Experience

Compare the traditional flow with the optimized solution offered by Vendor ID.

Traditional Flow: With Friction

Your App

Interruption

Exit to adobe.com

Flow with Vendor ID: Seamless

Your App

Instant Reading

Invisible process

Technical Operation

A look at the secure dialogue between your platform and Adobe services.

Authorization Data Flow

User Device

The app (via RMSDK) requests activation from Adobe server, identifying itself with your Vendor ID.

Adobe Server

Forwards an authentication request (SignIn) to your endpoint, passing user credentials.

Your Server

Validates the user and returns a response with their unique and stable identifier (UUID).

↓

4. Authorization Granted

Adobe creates an activation record and returns the license to the device.

Is Adobe Vendor ID Right for You?

Ideal for any organization that prioritizes user experience and brand control.

Publishers and eBook Stores

Offer a seamless shopping and reading experience, building customer loyalty and increasing conversions.

Educational Platforms

Provide students and teachers with instant access to study materials, eliminating technical barriers.

Corporate and Digital Libraries

Distribute protected documents and publications securely and transparently among your employees or members.

Frequently Asked Questions (FAQ)

Clear answers to the most common questions about implementing and using Adobe Vendor ID.

Adobe Vendor ID is a feature available to partners using Adobe Content Server. Its implementation typically does not involve an additional licensing cost from Adobe, but it does require an investment in development and infrastructure to create and maintain the authentication web service.

The main effort lies in creating your own secure authentication web service and modifying your application to use the new RMSDK APIs. Complexity varies depending on your existing infrastructure, but our team can provide you with an accurate estimate based on your case.

It is not a direct migration, but rather a coexistence. You can implement the "Join Accounts" flow so that your users can link their existing Adobe ID with their new Vendor ID-based account, maintaining access to all their previous content without issues.

Yes. All communication is done over HTTPS. Additionally, the system is designed so that you maintain full control over the authentication of your users. You never share your users' passwords with Adobe; you only confirm their identity and return a unique identifier.

Start Your Transition to a Better Experience

Our team of specialists is ready to guide you through every phase of the process, from planning to production deployment.

Contact a Specialist

Important Legal Notice

Adobe®, Adobe® Vendor ID, and Reader® Mobile SDK are registered trademarks or trademarks of Adobe Inc. in the United States and/or other countries.

This website, operated by PDI Consultores, provides technical and business information about Adobe® Vendor ID technology for informational purposes.

The information is presented "as is," without warranties of any kind, express or implied. PDI Consultores assumes no responsibility for any uses that may be made of this information. Other trademarks and trade names mentioned on this site are the property of their respective owners.