Skip to content

04. SQRL from a provider point of view page

Liam edited this page Oct 14, 2019 · 1 revision

In this page we will talk about the concepts of SQRL form a service providers point of view.

What is a service provider and am I one?

This page would classify you as a service provider if you answer yes to any of the following:

  • I have a website that allows/will allow users to login
  • I have a web app that allows/will allow users to login
  • I want to have some form of authentication on a set of data
  • The software I'm creating has customers that want to securely login

If you answered yes to any of these then this page would say that you are the ideal candidate for using this middleware.

Why should I use SQRL as a service provider

When you wish to allow users to login to your system securely and quickly without having to know passwords or manage passwords. *** YES, THAT RIGHT *** you did read that no more passwords and no more password leaks.

How much will it cost

Nothing it FREE yeah FREE SQRL has been created by Steve Gibson of GRC.com as a free and open authentication protocol.

What is a SQRL identity

An identity is a unique value that identifies an individual to site and can be associated with a user. An individual can have more than one identity per site.

How are there no passwords

OK so really there is one password but it’s the user’s password for there SQRL client and as a service provider you will never see this. This is a great thing as you will only ever get data that if leaked is of no help to a user.

What can I do if I need to scale up

If you have more than one application server or you might do at some point by design, then see the scaling and multi-server setups page for more information