Download the PHP package yuca/sso without Composer
On this page you can find all versions of the php package yuca/sso. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package sso
Short Description Simple Single Sign-On
License MIT
Homepage https://github.com/YucaApp/sso
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package sso
Single Sign-On for PHP (Ajax compatible)
NOTES: This version is forked from https://github.com/jasny/sso which improved with the following features:
- NGINX server support
- Whitelist IP
- Cache & Session 3rd party support
Jasny\SSO is a relatively simply and straightforward solution for an single sign on (SSO) implementation. With SSO, logging into a single website will authenticate you for all affiliate sites.
How it works
When using SSO, when can distinguish 3 parties:
- Client - This is the browser of the visitor
- Broker - The website which is visited
- Server - The place that holds the user info and credentials
The broker has an id and a secret. These are know to both the broker and server.
When the client visits the broker, it creates a random token, which is stored in a cookie. The broker will then send the client to the server, passing along the broker's id and token. The server creates a hash using the broker id, broker secret and the token. This hash is used to create a link to the users session. When the link is created the server redirects the client back to the broker.
The broker can create the same link hash using the token (from the cookie), the broker id and the broker secret. When doing requests, it passes that has as session id.
The server will notice that the session id is a link and use the linked session. As such, the broker and client are using the same session. When another broker joins in, it will also use the same session.
For a more indepth explanation, please read this article.
How is this different from OAuth?
With OAuth, you can authenticate a user at an external server and get access to their profile info. However you aren't sharing a session.
A user logs in to website foo.com using Google OAuth. Next he visits website bar.org which also uses Google OAuth. Regardless of that, he is still required to press on the 'login' button on bar.org.
With Jasny/SSO both websites use the same session. So when the user visits bar.org, he's automatically logged in. When he logs out (on either of the sites), he's logged out for both.
Installation
Install this library through composer
composer require jasny/ssoUsage
Server
Jasny\SSO\Server is an abstract class. You need to create a your own class which implements the abstract methods.
These methods are called fetch data from a data souce (like a DB).
The MySSOServer class can be used as controller in an MVC framework.
Alternatively you can use MySSOServer as library class. In that case pass option fail_exception to the constructor.
This will make the object throw a Jasny\SSO\Exception, rather than set the HTTP response and exit.
For more information, checkout the server example.
Broker
When creating a Jasny\SSO\Broker instance, you need to pass the server url, broker id and broker secret. The broker id
and secret needs to be registered at the server (so fetched when using getBrokerInfo($brokerId)).
Be careful: The broker id SHOULD be alphanumeric. In any case it MUST NOT contain the "-" character.
Next you need to call attach(). This will generate a token an redirect the client to the server to attach the token
to the client's session. If the client is already attached, the function will simply return.
When the session is attached you can do actions as login/logout or get the user's info.
For more information, checkout the broker and ajax-broker example.
Examples
There is an example server and two example brokers. One with normal redirects and one using JSONP / AJAX.
To proof it's working you should setup the server and two or more brokers, each on their own machine and their own (sub)domain. However you can also run both server and brokers on your own machine, simply to test it out.
On *nix (Linux / Unix / OSX) run:
php -S localhost:9000 -t examples/server/
export SSO_SERVER=http://localhost:9000 SSO_BROKER_ID=Alice SSO_BROKER_SECRET=8iwzik1bwd; php -S localhost:9001 -t examples/broker/
export SSO_SERVER=http://localhost:9000 SSO_BROKER_ID=Greg SSO_BROKER_SECRET=7pypoox2pc; php -S localhost:9002 -t examples/broker/
export SSO_SERVER=http://localhost:9000 SSO_BROKER_ID=Julias SSO_BROKER_SECRET=ceda63kmhp; php -S localhost:9003 -t examples/ajax-broker/Now open some tabs and visit http://localhost:9001, http://localhost:9002 and http://localhost:9003. username/password jackie/jackie123 john/john123
Note that after logging in, you need to refresh on the other brokers to see the effect.
