Skip to content

Latest commit

 

History

History
46 lines (32 loc) · 3.78 KB

README-PROD.md

File metadata and controls

46 lines (32 loc) · 3.78 KB
Raw

Sessionless Product Details

Introduction & Base Definitions

Authentication protocols (auth protocols) are gatekeepers that verify the identity of a person to give them access to specific programs or data. They include a set of rules or procedures that govern how data is transmitted across electronic devices. The most common uses of auth protocols are passwords, but others include one-time-passwords, biometrics, and magic links. [Click here for more information on identification and authentication.] (https://www.okta.com/identity-101/identification-vs-authentication/#:~:text=Identification%20is%20the%20act%20of,access%20to%20systems%20or%20privileges)

  • An Application Programming Interface (API) is a software intermediary that allows two applications to share data with each other
  • An API Key is a unique code that identifies and authorizes an application or user
  • An API Token is a piece of code that contains information about what privileges or sessions a user has access to
  • Encryption is the process of turning data into code to prevent unauthorized access [For more information on API Keys and Tokens, see here] (https://www.gomomento.com/blog/api-keys-vs-tokens-whats-the-difference/)

Problem Statement

Many auth protocols are client-server, where the client supplies some secret information (usually name and email address with a password) to authenticate requests. Encryption protocols, like https, provide some protection against data leaks, but they limit authentication opportunities (https for example, can't be used to connect embedded devices).

For example, setting up a payment processor like Stripe requires obtaining an API token and Key and connecting it to your product’s server. These keys can be compromised, creating security risks, and obtaining your key if it is lost is often impossible, which means starting the process from scratch.
  • Storage of secret information is platform dependent
  • API Key creation is also platform dependent for randomness
  • Language support for a given auth approach might be limited, locking companies into a particular tech stack
  • Requires users to be connected to the internet

Solution

Enter Sessionless, an authentication protocol (Sessionless Authentication Protocol, or SLAP), allowing for simplicity and flexibility by opening opportunities for indirect authentication.

With Sessionless, Services (websites, applications, and other digital services) can:

  • Authenticate users without gathering personal information which will
  • Reduce bounce rates
  • Remove security risks
  • Eliminate need for platform dependency to store secret information
  • Simplify authentication by removing key creation process
  • Authenticate users across devices such as computers, smart Tvs, Game Consoles, whether connected to the internet or connected via bluetooth devices

And Users can:

  • Decrease usage of password managers
  • Gain security

Use Cases

  • Decrease website bounce rates -

    The average bounce rate for B2C websites is 45%. “On certain pages, you may be asking visitors to do more than just read the content—like signing up for an account or filling out a form. If the page is asking for too much information or requires too many steps, then visitors may leave before taking any action; they'll have perceived too much cost before perceiving value.” With Sessionless, you can provide account continuity without asking for an email upfront, leaving the credential entering for after a user engages with your site.

  • Connect user accounts to single devices such as game consoles and maintain account continuity

  • Connect users to bluetooth devices such as controllers, keyboards, headphones, etc.