Single Sign-On (SSO) allows Broadsign Ayuda instances to function in environments where authentication has been centralized.
Upon completing this process:
- Broadsign Ayuda managers will no longer be able to create and manage their own user IDs and passwords within BMS, Splash, Juice and Alto. Also, all password management elements in Splash and Juice are eliminated.
- Broadsign Ayuda users will have to use their corporate e-mail accounts as their user names.
- Broadsign Ayuda users will have no Broadsign Ayuda log in screen.
With SSO enabled, all Broadsign Ayuda credential authentication is handed off to Okta. A valid BMS user with a username equal to the e-mail address registered in the authenticating service (for example Okta) is required to sign in to the Broadsign Ayuda platform.
Single Sign-On (SSO)
Alto and SSO
There are two methods.
- If SSO is enabled on Splash and Juice but not Alto, then Alto can continue to be used normally.
- If SSO is enabled for Alto, then users in Broadsign Ayuda must be created for the external users; however, do not enable any permissions for those users except Alto.
Permissions and Roles are Unchanged
What will not change are the assignment of roles and permissions in Broadsign Ayuda. Administrators can continue to assign roles and permissions for Splash and other Broadsign Ayuda products.
