Platform transition
Adobe Content Server is now ByteBooks
Adobe transferred its eBook platform to Wipro in July 2025. Adobe ID sign-in for Adobe Digital Editions ends on 23 June 2026. Here is what actually changes, and what your team has to do before then.
Timeline
What has happened and what is coming
Platform handed to Wipro
Adobe transferred maintenance, updates, customer support, feature development and roadmap for Adobe Content Server and RMSDK to Wipro Engineering — Connected Services, formerly HARMAN Digital Transformation Solutions. The service now operates as ByteBooks.
Support and downloads move
Support, product downloads and account management for the eBook platform are handled through ByteBooks rather than Adobe.
Adobe ID stops working for Adobe Digital Editions
After this date Adobe ID is no longer used to sign in to ADE. Readers create a ByteBooks ID using the same email address as their Adobe ID, and their existing eBook licences carry across to that account.
Re-authorisation on new devices
Devices already authorised keep working. Signing in on a new device, or after a credential change, needs the ByteBooks ID. RMSDK applications will receive the error E_ADEPT_RESET_PW_REQUIRED when a reader presents a credential that has not moved.
What does not change
The alarming version of this story is the wrong one. No book stops working, no file has to be re-encrypted, and Adobe Digital Editions itself is the same application it was.
- Your files
- Already-encrypted EPUB and PDF/A titles remain valid. Nothing is re-issued.
- Your readers' libraries
- Existing licences move to the ByteBooks account created with the same email address.
- Adobe Digital Editions
- Same application, same version. Only the sign-in behind it changes.
- Your relationship with DMR
- Unchanged. We continue to operate the content server and fulfil your titles.
What you have to do
Three of these are your job. All three are things DMR can do with you.
- Tell your customers
- Anyone currently signing in with an Adobe ID needs to know, in your words, before they hit the error.
- Handle the new error code
- If you ship or embed an RMSDK application, handle E_ADEPT_RESET_PW_REQUIRED explicitly and route the reader to the right instruction.
- Brief your support desk
- Give the desk the script, the screenshots and the escalation path before the volume arrives, not after.
- Test the path end to end
- Buy one of your own titles, sign in with a ByteBooks ID, re-authorise a device, confirm the library appears.
How we help
Transition support from DMR
Reader communications
Draft email and help-centre copy explaining the ByteBooks ID in language your readers use, localised if you need it.
Support-desk briefing
A one-page script, the error states your desk will see, and the exact re-authorisation steps for ADE on Windows, macOS, iOS and Android.
Application review
If you ship an RMSDK app, we review where the new error surfaces and what your UI should say when it does.
End-to-end test against your titles
We run the full purchase, sign-in, authorise and open cycle on your own catalogue before the cut-off, and give you the result in writing.
Questions we are being asked
Do I need to re-encrypt my catalogue?
No. The change is to reader authentication, not to content encryption. Files already in the reserve remain valid and are fulfilled exactly as before.
Will readers lose the books they have already bought?
No, provided they create their ByteBooks ID with the same email address as their Adobe ID. The licences are attached to that address and carry across.
What happens to a device that is already authorised?
It keeps working. The one-time setup is only needed when signing in on a new device or after a credential change.
We have readers whose Adobe ID email no longer exists. What then?
That is the case worth finding early, because it needs a person rather than a self-service flow. Identify those accounts now; Wipro's eBook support handles the email mismatch cases.
Does this change what DMR charges us?
No. The transition does not alter your plan or your per-fulfilment terms.
Is this a good moment to review our DRM strategy generally?
It usually is. Most publishers we talk to also have unprotected video sitting somewhere, and the two questions are cheaper to answer together. See video DRM.
Book a transition review
Forty-five minutes, your catalogue and your support desk on the call. You leave with a dated checklist and the reader-facing wording already drafted.