website logo
➡️ purplepublish.com
Overview
Setup
Editorial
Experience
Growth
Developers
Navigate through spaces
⌘K
Team, Users, Roles, Rights
Team Management in Purple Manager
Overview of roles & rights in Purple Manager
Overview of roles & rights in Purple Hub
Change the role of a user in Purple Hub
Invite a new user to your team and assign a role in Purple Manager
Apps, App Stores and Purchases
App Design
Purple Manager Basic Settings
App Stores and Subscriptions
Coupon code function
Translations
Create a publication in Purple Manager
Configure PDF download for e-paper module in web
Configure PDF download for single pages in e-paper in web
Set up 'Background publishing'
Set up a custom domain for article preview in Purple Hub
Issue downloads in app
Consent Management for Purple Apps
Entitlement
Entitlement: Preconditions for connecting with Purple
Entitlement Integrations
Firebase Dynamic Links
Apple Setup
Android Setup
Purple Manager Setup
Creating a Dynamic Link
Firebase Setup
Configuring the Mapping
Deferred deep linking
Docs powered by archbee 

Entitlement: Preconditions for connecting with Purple

15min

Purple Manager



Summary

In this article, you get an overview about all the necessary information, that is needed by Sprylab, to connect your external Entitlement System with Purple. As soon as we have received all your input, we will do the steps needed to make your external Entitlement System work with Purple. If you are in doubt about any point in the list, get in touch with your Project Manager.



Preconditions

Required documents

  • Documentation of the interface
  • Example calls/example requests and -answers

Helpful info

  • Type of interface? Ex: REST API, oAuth2/OpenID, SOAP
  • URL of the test system
  • URLs of the live system?

Limitations, type of access for the user

  • What is the response from the Entitlement Server (single issues, IDs, streaming/full access, publications, time periods)
  • For which response from the server, should we enable the user what exactly?

Access data for the interface

  • API keys
  • Client certificate
  • Basic Auth user

Required test users

  • 1 user with access
  • 1 user without access (or expired)
  • 1 user had a subscription and access to past issues
  • 1 user with access to a specific publication

It is best practice, that the test users remain stable and do not expire. This is important for later tests!

Special logics

If necessary, special logics need to be custom developed

  • Maximum number of devices logged in at the same time desired? -> The Entitlement Server must be able to do this, the interface must offer the possibility to send the device IDs.
  • Is the Synchronization of In-app purchases with the Entitlement desired? E.g. user can register without buying, user must buy etc.
  • Redirects from the web to the app, with transfer of a token to the app so that the user is logged in directly.
  • Is End-to-end encryption desired? This means, user data is encrypted directly at the time of entry and only decrypted at the Entitlement Server.

Since 31.1.22, a function that allows the user to delete his data after registration, must be offered.

Layouts

  • Login mask
  • Registration mask

We also offer our own interface: Purple Standard Entitlement Interface



Updated 25 May 2023
Did this page help you?
Yes
No
PREVIOUS
Entitlement
NEXT
Entitlement Integrations
Docs powered by archbee 
TABLE OF CONTENTS
Summary
Preconditions
Required documents
Helpful info
Limitations, type of access for the user
Access data for the interface
Required test users
Special logics
Layouts
ImprintPrivacy Policy
© Sprylab Technologies GmbH 2022