Adobe Vendor ID specifications

Adobe Vendor ID is a web service specification, so it does not include any deliverables. There is no software or API to be installed. The spec is provided to vendor ID customers, and provides detailed information on the format of the web service requests and responses.

Vendor ID is an authentication service that allows for an activation and authentication process requiring only one login.

To learn more, see the description of the Adobe Vendor ID on the ACS product page, or this blog article.

Compatibility between Vendor ID, RMSDK and ACS

Vendor ID version is not directly tied to either the RMSDK version or the Adobe Content Server's version.

Customers must use RMSDK version 9.2 or later for vendor ID, and ACS version 4 or later.

What does the customer need to do?

A Vendor ID customer must implement three web services according to the vendor ID spec. These web services will respond to Adobe's SignIn request for the purpose of validating the vendor and the user. You should have received the Vendor ID spec when you ordered your Vendor ID license.

See RMSDK documentation on Activation on how to use Vendor ID instead of Adobe ID to activate a user account. This documentation is included with the RMSDK software installation package.

What web services need to be implemented?

More details are provided in the vendor ID spec. In summary here, the Vendor ID provider need to implement a few web services that can accept requests over the web and respond accordingly. Three services are:

  1. Accept request to authenticate a user account and respond with a valid user UUID
  2. Optionally authenticate user by auth token
  3. Report user description when given a user's UUID
  4. Status response

Choosing a port number for web services URL

Because the actual client of a Vendor ID service is an Adobe-hosted server, the firewall rules are very strict. We recommend that you use one of the standard http-related port numbers, such as 80, 8000, 8080, 443, 8443.

Getting a Node ID from Adobe

The Vendor ID customer will need a hex encoded Node ID to implement the web services. After you buy a Vendor ID license, provide Datalogics with a name to identify the vendor and this name will be used to generate a Node ID. This Node ID is used in implementing the Vendor ID web services.

Testing and Approval

After the Vendor ID web services are implemented, ask your Datalogics representative to test the services. After the testing is complete, Datalogics will notify Adobe Systems to activate the given Vendor ID.

The web services are straightforward. You can use unit testing to check the content and format of the request and response messages against the Vendor ID spec while you are implementing the Vendor ID.

Adobe Content Server

  1. Adobe Content Server
  2. Release Notes
  3. System Requirements
  4. Upgrading ACS from 4.0 to 4.1 or 4.2, and to 5.0, 6.0, and 6.5
  5. Adobe Content Server: General
  6. ACS and eCommerce Stores
  7. Activations in Adobe RMSDK and Adobe Digital Editions
  8. Adobe Vendor ID specifications
  9. Vendor ID Workflow
  10. Changing the fulfillment URL in ACS
  11. Developing and Using Packaging Tools in ACS
  12. Adding Digital Rights Management (DRM) permission tags to eBooks when packaging them
  13. How does passhash work in Adobe Content Server and RMSDK reader applications?
  14. Join Account Workflow and Multiple Activations
  15. Opening NOOK books in Adobe Digital Editions
  16. PDF Compatibility, Adobe Digital Editions and Adobe Content Server
  17. Removing the Adobe Digital Edition authorization when it fails (erase authorization)
  18. Replacing an Existing Book in ACS
  19. Setting up ACS with Microsoft SQL Server Database
  20. Setting up Books for Loan in ACS
  21. Working with EPUBVER
  22. Working with Readium
  23. Adobe Content Server: Errors and Error Messages
  24. Admin Console Login Error
  25. Admin Console in ACS not handling large numbers of books
  26. Could not load database driver, ACS Status check 404/500 error
  27. E_ACT_SCHOOL_MODEL_INCOMPATIBLE_SOFT error, incorrect version of ADE
  28. E_ADEPT_CORE_LOAN_SIGNATURE error from Adobe Content Server
  31. E_ADEPT_DOCUMENT_TYPE_UNKNOWN error from ADE or other readers
  32. E_ADEPT_IO error from Adobe E-Book Reader Applications
  33. E_ADEPT_MISSING_ELEMENT from Adobe Content Server
  34. E_ADEPT_NO_TOKEN error Getting License: License Server Communication Problem:
  35. E_ADEPT_REQUEST_EXPIRED: Ebook download error from ADE or other e-readers
  37. E_ADEPT_UNKNOWN and Out of Memory error from ACS packaging
  39. E_LIC_CONNECTION_PROBLEM or Adobe Signing Server returns No Running error
  40. E_LIC_LICENSE_SIGN_ERROR from Adobe Content Server
  41. E_LIC_WRONG_OPERATOR_KEY Error from Adobe Content Server
  42. E_PACK_DATABASE Error from Adobe Content Server packaging
  43. E_PACK_DUPLICATE_SRC Packaging Error
  44. E_PACK_ERROR "MALFORMED" or "NullPointerException"
  45. E_PACK_ERROR null error from packaging books in ACS
  46. E_PACK_INCORRECT_FORMAT error from packaging
  47. E_URLLINK_AUTH error from ACS download link
  50. EPUB file failed to package - Error about incorrect language field
  51. Foreign Key Constraint Error when trying to delete resources in ACS
  52. Fulfillment status check 500 error - P12 BadPaddingException: Given final block not properly padded
  53. Fulfillment status check returns HTTP error code -500 or 404
  54. GBLINK_AUTH_SIGNATURE_NOMATCH error with ACS GBLink sent through email
  55. IO Error on Network Request? Error #2038
  56. Java Memory Error, Packaging Large Files
  57. Login Error: Change or Reset Admin Console Password
  58. MySQL error in your SQL syntax, check manual for “????”
  59. Packaging error, E_PACK_FILE_READ Permission Denied
  60. Print or copy permission shows zero pages in ADE on second device or computer
  61. Required Property Missing, ACS Status Check returns 404 error
  62. Unexpected end of ZLIB input stream
  64. XMLSigningSerializer.php generates incorrect <hmac> code in ACS

Feedback and Knowledge Base