Thank you for the constructive feedback, ViperMax.
Everything thing is there, just not in a format most people are used to.
I think you need improve youre thread
because nothing explain coin, plan project, roamap, dev team and more
```````````
```````````
Today, I am going "The Extra Mile" learning about SSO:
```
Single Sign-On (SSO) Terminology and Concepts
Unless you have used a Single Sign-On (SSO) system before, there is some terminology that you will need to understand to be able to work with this software product.
Field - A place to store information about a user. First name, last name, e-mail address, location, etc.
Tag - A place to store administrative access permissions to other systems or special flags for any purpose. Primarily for manually added permissions and roles. Forum moderator, editor, etc.
Provider - An access authentication and authorization mechanism. Generally adds entries to the administrative interface and the end-user interface.
Provider ID - An ID that a provider provides during authentication with the SSO server that, when combined with the provider, uniquely identifies an associated user account.
User Account - Stores a unique ID, provider name, provider ID, fields, and associated tags.
Endpoint - A URL that exposes the API of the SSO server.
API Key - Consists of a short string and a numeric ID. API keys are used during SSO client installation and grants access to the SSO server endpoint.
API Secret - A secret, shared token used for encryption of data sent across the wire. The API secret is stored alongside an API key and used during SSO client installation and grants access to the SSO server endpoint.
Namespace - Each API key has a namespace. When a user signs in to one application, they will be signed in automatically if they visit another application using another API key in the same namespace.
The SSO server separates login information from account information. The SSO server only knows what a Provider and a user account are, but not a login. Today, a Provider will implement a standard login system. However, if software developers figure out a way to eliminate usernames and passwords in the future, this SSO server can easily adapt to the new approach via a new Provider.
The SSO client communicates with the SSO server using an API key and encrypts the transmission using the associated API secret.
http://barebonescms.com/documentation/sso`````````````
`````````````
$200 Golden ICO credits!
Who wants to donate a working demo, including the forum plugin?
Demo of this:
The Single Sign-On (SSO) server and client is a complete SSO system in a single, self-contained package and does NOT require Barebones CMS to function.
Open-source download here:
http://barebonescms.com/documentation/ssoPlease, PM me first, since I will already be working on it.
