Single Sign-On

There are two main reasons for using JRNI single sign-on:

1. You want to enable customers to use their existing authentication credentials to be authorised to make new appointments or make changes to existing ones.

2. You want to enable staff to use their existing authentication credentials to be authorised to make administrative changes.

In both cases a token will need to be generated that contains details of the customer or staff member. This SSO token is exchanged for an Auth-Token and the individual will be added to the system if they don’t already exist.

Ruby SSO Token Generation Example

C# SSO Token Generation Example

Java SSO Token Generation Example

Member Login

curl -X POST \
  https://{host}.bookingbug.com/api/v1/login/sso/{company_id} \
  -H App-Id:1234 \
  -H 'Content-Type: application/json' \
  -d '{
      "token": "abcde"
  }'

Admin Login

curl -X POST \
  https://{host}.bookingbug.com/api/v1/login/admin_sso/{company_id} \
  -H App-Id:1234 \
  -H 'Content-Type: application/json' \
  -d '{
      "token": "abcde"
  }'