SSO Release (deployed 7/22/2022)

Requirements

• A modern web browser updated to a current release. Tested browsers include:
  • Google Chrome Version 102.0.5005.115 (Official Build) (x86_64)
  • Apple Safari Version 15.1 (17612.2.9.1.20)
  • Mozilla Firefox Version 101.0.1 (64-bit)
• ShotFlow user seat with access to at least one app
• For local capture work: ShotFlow Capture Version 2.2 and higher (please note older releases of ShotFlow Capture will no longer connect after this platform release)

What’s New?

• Initial Support for Single Sign-On (SSO). This is ShotFlow's first release of Single Sign-On (SSO) support for clients who wish to leverage their corporate session and user authentication service with ShotFlow. SSO permits a user to use one set of login credentials (email and password) to access multiple corporate applications securely. Note that SSO systems and standards vary widely, and ShotFlow does not guarantee support for every SSO provider, method, and capability. Please contact support@shotflow.com to learn more about utilizing SSO in your ShotFlow instance.
• Added support for barcode fields to List Search "Show Difference" function. The new "Show Difference" checkbox for List Search, displaying any value(s) that did not match the input values, was deployed last month without support for barcode value fields. This field type is now supported for this function, which will make a lot of people happy.

What Did We Change?

• Log-in process has been change to support SSO. When accessing any ShotFlow environment, the log-in screen is now split into separate steps, where the user's email is entered and submitted. If the user/client does not utilize SSO, the password is now entered on a second screen. For clients with SSO, no password entry will be required if the SSO authentication is successful.
• Logic for determining if a Set is occupied on the same computer. Previously if a user did not log out of a local Capture session, and another user tried to use the same computer to log in, the Set would report as still occupied. This logic has been modified so the Set should be cleared when the first user's authorization token expires.