why publishers need independent identity & access management
Post on 21-Jan-2018
318 Views
Preview:
TRANSCRIPT
Why publishers need independentIdentity & Access Management
Tim Lloyd, Founder & CEO of LibLynx
Identity & Access Management = IAM
Identity Management = “Who are you?”
Authentication methods include
username & password,IP ranges, and Single
Sign On (SSO)
Access Management = “What can you access?”
Authorization logic includes validating
online purchases and subscription start &
end dates
5 reasons why IAM is a critical tool for growth
5 reasons why IAM is a critical tool for growth
1) Enable sales to new customer types
● Individuals e.g. ORCID, social logins
● Institutions e.g. Shibboleth, OpenAthens
● Corporates e.g. LDAP, SSO, ADFS
● Public libraries e.g. SIP2, library card matching
5 reasons why IAM is a critical tool for growth
2) Enable product/pricing innovation
● Time-based & perpetual subscriptions
● Single title sales models e.g. PDA
● Metered and concurrent access models
● Vouchers, tokens and coupon codes
5 reasons why IAM is a critical tool for growth
3) Promote Usage & Renewals
● Reduce access friction to promote usage
● Expand range of access scenarios supported
● Quickly identify & resolve access failures
5 reasons why IAM is a critical tool for growth
4) Integrate new acquisitions
● Deliver a consistent access experience to users
● Seamless, low friction access across products
● Unify access management
● Centralize data management
5 reasons why IAM is a critical tool for growth
5) Understand user needs
● Capture valuable access & usage data
● Centralize data management
● Behavioural analytics reveal user preferences
● Drive user personalization & engagement
Distribution channels are splintering
Distribution channels are splintering
One platform doesn’t fit all needs
● Content e.g. text, audio, video, images, data
● Audience e.g. author, member, user, customer
● Technology e.g. open source, in-house, vendor
Distribution channels are splintering
IAM must be unified, and independent of:
● Markets & customer types addressed
● Business and pricing models adopted
● Technology
● Platform & vendor
However, in-house IAM lack investment
However, in-house IAM lack investment
• Low priority vs user content & features
• Often born with minimum viable features
• Degrade over time
• High opportunity cost of support
… making future enhancements costly
• Architecture not designed for future needs
• Backlog of fixes awaiting prioritization
• Reduced developer familiarity with code
• Original developers may have left …
Traditional vendor solutions are monolithic, inflexible and expensive
Most vendor IAM is baked into platforms
● Typically does one job well
● Designed for a single platform
● Not technology/platform agnostic
● Can’t unify IAM across multiple platforms
Traditional vendor solutions are monolithic, inflexible and expensive
Traditional dedicated solutions perform poorly
● Inflexible (not architected for modular expansion)
● Expensive to integrate (not API-centric)
● Often require additional fees for multi-tenancy
● Often tethered to related vendor platforms
Traditional vendor solutions are monolithic, inflexible and expensive
LibLynx offers an Independent alternative
A true, unifiying IAM solution
• Technology & vendor agnostic
• API can be understood in minutes
• Freedom to choose platforms and technologies
that best fit each publishing use case
LibLynx offers an Independent alternative
The agility to be innovative
• Simple API call to manage visitor requests
• Quickly & easily support new customer types
and business/pricing models
• Free up valuable technical resources
LibLynx offers an Independent alternative
Only pay for what you use
• Usage-based pricing delivers a highly featured
solution at a fraction of the cost
• Low volume use cases become viable
• Volume discounts ensure pricing scales affordably
learn more at www.liblynx.com
Image Credits:● La alegría del número 8 by mingusmutter (used under cc-by-sa-2.0 license)● Splintered Post at Aberlady bay by Ronan (used under cc-by-nc-nd-2.0 license)● desk by Michael Cory (used under cc-by-nc-2.0 license)● stonehenge by Jeremy Sorrells (used under cc-by-nc-2.0 license)● lappland hike 67 by Raphaël Vandon (used under cc-by-nc-nd-2.0 license)● Cheetah Run by David Siu (used under cc-by-2.0 license)● Candy by Kevin Tao (used under cc-by-nd-2.0 licence)
LibLynx Connect:secure, cloud native IAM
or email us at info@liblynx.com
top related