Introduction
This user guide describes the service provided for our partners, where your users can sign into the Site Builder, and optionally be redirected directly into the builder for an existing site, using your website's credentials. This is generally known as a "Single Sign-On", or SSO, system.
Contained in this document:
Access requirements
Access has to be approved and enabled within your private label
You will be given an OAuth "public" key (
CONSUMER_KEY
) and a "secret" key (CONSUMER_SECRET
)You will also be given a base URI, signifying where the widget javascript requests will be made:
BASE_WIDGET_URI
: The base URI for the single sign-on (logs the user into the site management interface)
Prerequisites
The platform uses portions of the OAuth protocol to verify that a user has access to it's SSO system. You will need to install an OAuth library that fits in with your server technology. There are several linked to the OAuth code website.
The widget examples shown use the jQuery JavaScript library to render itself, but any form of javascript can be used to interact with the widget
Request Parameters
Your code will generate a signed URI, which is the main way that the API interacts with your web page. The following are the required GET request parameters for both SSO and direct-to-builder access type:
For direct-to-builder access, the following parameters are also required:
Code examples
All of the examples utilize the following jQuery snippet for displaying the SSO links on a page.
show-links.js
show-links.js
Python/Django example
The following example uses Python and Django to generate the code necessary for the login widget to render, and direct links to the builder for specific sites. It uses the python oauth library to generate the signed oauth urls.
views.py
views.py
index.html
index.html
Last updated