Introduction

SCView offers the convenience of Single Sign-On (SSO) integration, enabling users to log in using their Microsoft or Google accounts. This feature simplifies the authentication process and enhances security by leveraging existing corporate credentials. Understanding the setup process is crucial for administrators to facilitate smooth access for users while maintaining secure and efficient operations.


A. Problem Statement

Managing multiple usernames and passwords for different systems can be cumbersome and pose a security risk due to password fatigue and potential for weaker password choices. For organizations utilizing SCView, the need to streamline the user authentication process while enhancing security is paramount.


B. Solution

Implementing SSO in SCView addresses these challenges by allowing users to access their SCView accounts using their existing Microsoft or Google credentials. This integration not only simplifies the login process but also aligns with modern security practices by reducing the number of passwords users need to manage.


SSO (Single Sign On) will allow a user to login using their Microsoft or Google account.


There are a few steps to start using this option.


NOTE: You must be an admin to make these changes.


1. Go to Admin > Users.



2. Highlight the user for whom you wish to enable SSO and click Edit.



3. Change the User ID field to the user's Gmail or Outlook email address. When the User ID is changed, it will wipe out the Password and Confirm Password fields. These fields can now be ignored. Change the Auth Type dropdown from Classic to Google or Microsoft.



4. A Confirm Change popup will appear. Click Yes to confirm this change for the user.



5. Click Save.


When using Google, Microsoft, or OneLogin as the Auth Type, you will need a valid email address or the system will not allow you to save the user. Format example: testuser@domain.com




6. Notify the user that SSO is now enabled for their account. For the user to log in using SSO, they will choose the Google or Microsoft tab (whichever email service applies to your district), enter their Database code, then click Login. No User ID or Password will be required moving forward.



7. The user will be directed to their Google or Microsoft login. Upon successfully logging in on this secondary page, they will be redirected back to SCView and will be logged in.



C. Best Practices

  1. User Information Update: Ensure that the User ID for each account is set to the user's official Gmail or Outlook email address as this becomes crucial for SSO functionality.
  2. Authentication Type Selection: Accurately change the Authentication Type to either Google or Microsoft based on the email service provider used by the district.
  3. Verification and Confirmation: After making changes, verify through the Confirm Change popup and ensure the accuracy of settings before saving.
  4. Communication with Users: Notify users effectively once SSO is enabled, providing them with clear instructions on how to access their accounts moving forward.
  5. Documentation and Logging: Keep detailed logs and documentation of all configuration changes and user communications for auditing and troubleshooting purposes.


D. Troubleshooting

  • SSO Login Failures: If users report issues with logging in via SSO, verify their User ID is correctly formatted as an email address and that the Auth Type matches their email service. Check for service disruptions in Google or Microsoft services as well.
  • Authentication Type Errors: Should there be problems related to incorrect Authentication Type settings (Google or Microsoft), revisit the user settings in Admin > Users and confirm the correct option is selected.
  • User Notification: In cases where users are unaware of the shift to SSO, reissue communications detailing the login changes and provide assistance as needed.



Conclusion

Implementing Single Sign-On for SCView empowers organizations to enhance security and streamline user access through the integration of enterprise-level authentication mechanisms. By following the outlined steps and best practices, administrators can ensure a seamless transition to SSO, significantly improving user experience and maintaining robust security standards. Should any issues occur during or post-implementation, the troubleshooting tips provided will be instrumental in resolving them efficiently. This proactive approach towards modern authentication practices like SSO is essential for optimizing system accessibility and security in today's digital landscape.