-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
You can see the list of known profiles here: https://readium.org/lcp-specs/registries/profiles
The profile used by the LCPL file is listed under the JSON key {
"provider": "https://www.edrlab.org",
"id": "69f0547a-edef-4a99-8212-7512745268b1",
"issued": "2021-11-08T11:00:28Z",
"encryption": {
"profile": "http://readium.org/lcp/basic-profile",
... If you have any issue making your |
Beta Was this translation helpful? Give feedback.
-
To add to this discussion: the LCP module exists in two variants: Test and Production. Developers willing to try an LCP development start with the Test LCP module, using instructions given by EDRLab (contact (at) edrlab.org). And they test their development with Test licenses. If they try to open a Production license, they will get the error above. |
Beta Was this translation helpful? Give feedback.
To add to this discussion: the LCP module exists in two variants: Test and Production.
The Test variant can open Test LCP licenses only. Test LCP licenses are generated by an LCP Server in Test Mode, e.g. the codebase directly downloaded and compiled from Github (https://github.com/readium/readium-lcp-server).
The Production variant can open Test and Production LCP licenses. Production LCP licenses are generated by an LCP Server in Production Mode, e.g. the codebase downloaded from Github, modified to handle the Production Encryption Profile 1.0 defined by EDRLab and compiled.
Developers willing to try an LCP development start with the Test LCP module, using instructions given by EDRLab (…