Knowing the power of learning by doing that lies within "copy-paste", we have prepared and will expand an array of tools and examples to make integrating SSQ signon into your systems super-easy. Each example includes:
We do provide some tools along with the examples to enable integrating with SSQ signon with just a few (ideally - 1) lines of code. However, in the end all you need to integrate with SSQ signon is an HTTP client.
An SSQ singon authorization server is not meant to store any user records by itself. However, issuing, refreshing and revoking access tokens will obviously require querying a users database at some point. To do this, every SSQ signon module utilizes a user endpoint. Currently, 2 types of user endpoints are supported:
The settings section of every SSQ signon module is divided into these subsections:
Once you've registered with SSQ signon and created your first module, check the best practices section of the module admin app for useful hints on how to get the most safety, performance and value out of your new authorization server.