This article shares how Single Sign-On (SSO) and Open Authorization (OAuth) can be leveraged within Zammo. Specifically, we cover the following topics:
Further details are also provided that detail the main components involved when setting up Zammo to use SSO and OAuth.
SSO and OAuth share some similarities but are two different things.
Single Sign-On (SSO)
Single Sign-On (SSO) is not an industry-standard protocol. SSO is an authentication and authorization process that lets users securely authenticate into multiple applications, websites, or web services using a single set of credentials.
For example, SSO could be used to let employees log in to their account on your website, and access an internal intranet, custom web application, or web portals such as SharePoint.
In the video below you can see SSO further in action. A user can perform a login on your site or within your system directly. When the chatbot is accessed, authorization is passed to the webchat and profile, or other relevant, data from the logged-in account can already be used to greet the user and access any relevant information such as their picture and name: