Single-Sign-On (SSO) is a power authentication tool that allows a centrally controlled user ID and
password to grant access to multiple applications and systems. The end-user is freed from the
burden of remembering multiple user ids and passwords which may have different requirements
and aging requirements. SSO limits the possibility of an end-user writing down a list of credentials
for various applications and potentially leaving them exposed. The tool simplifies administrative
management of assigning multiple end-user IDs and helps with troubleshooting user access issues.
However, SSO system management does require additional expense and specific skills, knowledge,
and training to administer. SSO can be seen as a vulnerability, as a compromised account gains
access to all the systems available to the account owner under the SSO umbrella.
As mentioned in other discussions, I have provided IT consulting services to car dealership
franchises, and SSO was deployed to all employees. This allows them to access the dealership
network resources (shared drives, printers, network access), Microsoft 365 applications and email,
and the dealership’s ERP with one user ID and password. Unfortunately, the manufacturers’
websites and applications do not support SSO, but end-users have expressed satisfaction with only
juggling two IDs rather than multiple. For users that have direct access to financial systems or
customer information within the ERP, we’ve also deployed Multi-factor Authentication (MFA), to add
an additional layer of protection over that data. I hear grumbles from time to time regarding the
minor inconvenience, but most understand and appreciate that their personal information that is
housed in the system is protected as well as that of the company and their customers.
