Website logo
➡️ purplepublish.com
Overview
Support
Setup
Editorial
Experience
Growth
Developers
Expert
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
iOS App Test & Submit
Coupon code function
Translations
Create a publication in Purple Manager
Configure TTS for content
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
Connect Desk-Net to your Purple Hub
Issue downloads in app
Consent Management for Purple App & Web
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

Entitlement: Preconditions for connecting with Purple

5min

Purple Manager



Summary

In this article, you get an overview of 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.



Requirements for the estimation phase

  • Description of access logic
    • What types of access are needed?
    • Is it a Netflix model?
    • Are contents unlocked on a publication date- / publication- / single content-basis?
  • Type of API?
    • e.g. REST-API, OAuth 2.0 / OpenID or SOAP
  • Documentation of interfaces
    • For custom REST APIs:
      • description and examples for all
        • request and response parameters
        • status codes
        • response bodies
    • For OAuth 2.0 / OpenID:
      • Is provider auto-configuration supported?
      • If not: description of all endpoints, request and response parameters, status codes and response bodies
  • Any other individual logic (limitations of login counts, login via deep links etc)

Requirements for the implementation phase

  • All of the requirements from the estimation phase
  • Prepare and provide information on the test environment
    • For OAuth 2.0 / OpenID:
      • Allow all redirect URLs from Entitlement Integrations
      • URLs of endpoints
      • Client ID / Secrets
    • For REST-APIs:
      • URLs of endpoints
      • Credentials, e.g. Basic Auth, Client Certificates or API Keys (if needed)
  • Test users for all possible combinations of access
    • Examples:
      • user with access
      • user without access (or expired access)
      • user with an expired subscription but who should still have access to past issues
      • user with access to specific contents only (ie. certain publications)

We can only integrate with external systems when certain performance thresholds are met. Our systems have strict limits for requests to external systems.

  1. Any request taking longer than 3s will be cancelled.
  2. Furthermore our systems will automatically disable an integration, if more than 50% of all requests within a timeframe are slower than 2s. It will stay disabled until requests are faster again.

We reserve the right to adjust these limits in case we notice negative impact on our systems and/or other customers.

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

We also offer our custom interface: Purple Standard Entitlement Interface



Updated 08 Dec 2023
Did this page help you?
PREVIOUS
Entitlement
NEXT
Entitlement Integrations
Docs powered by Archbee
TABLE OF CONTENTS
Summary
Requirements for the estimation phase
Requirements for the implementation phase
Docs powered by Archbee
ImprintPrivacy Policy
© Sprylab Technologies GmbH 2023