Implementing Single Sign On (SSO)

Introduction

Bud supports the ability use SSO integration with other systems using a range of implementations, with a range of industry standard protocols.

SSO support is defined as the ability for a user to sign on to one system and be able to seamlessly transition into another entirely separate system without needing to enter new credentials. This does not include the transfer of data between systems e.g. course booking and results as this would fall into the category of integration.

Please speak with your Customer Success Manager if you are considering an SSO integration.

Supported Protocols

Bud supports the following SSO industry standard protocols:

  1. OpenID Connect/OAuth2.0
  2. SAML 2P

Implementation

Bud typically acts as the identity provider providing SSO into various platforms holding learning content. A typical use case would be for a user to login to Bud, access a learning plan and an activity, where a URL link is clicked, opening the select 3rd party where the user is passed directly into the platform without the need to login a second time.

Bud can also support SSO where Bud acts as the service provider. A typical use case would be for a user to authenticate through an intranet into the Bud platform, or a “login via” button on the main login page. This is often present in several web applications as “Login via” Facebook, Google, Office 365 as common implementations.

Each implementation is unique and subject to 3rd party support and compliance with industry standard protocols.

Please speak with your Customer Success Manager if you are considering an SSO implementation.

Was this article helpful?

0 out of 2 found this helpful

Have more questions? Submit a request