Single sign-on … so what?

Over the past few weeks we have been rolling out myUChicago to students across the University, and with it a range of new and integrated tools designed to help simplify the way you access UChicago systems and information on the Web. One of those tools is Single sign-on (SSO).

Since not everyone is familiar with Single sign-on or the benefits it brings, we thought it might be a good idea to give a brief overview of what it is, what it does, and how it will be helpful to you as you dig into myUChicago and explore all it has to offer.

The Basics

Single sign-on (SSO) was developed to simplify access to multiple password-protected systems, minimizing the issues associated with managing numerous usernames and passwords. OpenID and Microsoft Passport (now called Windows Live ID) are examples of SSO services.

SSO is a property of multiple related, but independent systems that allows a user to log into one system, and then have access to all other related systems without logging in again. Sign in once, and then you’re done.

Why this matters

Imagine not having to manually log into 15 different systems just to complete a single task. Imagine access to password-protected systems aggregated to a single location. How much easier would that make things? Based on what we’ve heard so far, a lot easier. And that’s what Single sign-on provides: and easier way to conduct your University business.

Of course, as much as we wish it were just that simple, there are a few things to keep in mind when it comes to Single sign-on.

It’s a two way street

In order for Single sign-on to work across systems, it needs to be implemented on both ends. Meaning, just because Single sign-on is operational in myUChicago, doesn’t mean it will work in ever other system myUChicago links to.

While we are currently working with other University divisions to determine which systems can/will be brought online with SSO, we are at the beginning stages of a process that will take time to implement. So please be patient, and let us know where you think SSO would be the most helpful to you.

Safety First

Single sign-on is a useful, convenient tool that makes it easy to get in and out of password-protected systems. Unfortunately, that means it’s also easy for others to get in and out of multiple systems using a single log in, should you walk away from a personal or public computer without completely ending your session.

The myUChicago implementation of Single sign-on has a 30-minute idle time-out to help minimize the risk (do nothing for 30 minutes on the site and it kicks you out). And while that is much better than the standard 8-hour window of many SSO systems, in order to more fully protect your information, it is important that you completely exit your browser application when you are finished using myUChicago. If you don’t, your session could remain active, making your information vulnerable.

And because security is a top priority when comes to your personal information, it is important to note that there are some University systems that will NOT participate in Single sign-on. We will be sure to keep you informed as those systems are identified.

What to look for

We have tried to make the integration of Single sign-on very visible within the context of myUChicago. Links in the site that make use of Single-sign on are marked by the following icon:

When you see ‘Single sign-on enabled,’ you know the outlying system will not require you to log in again. Simple.

Who’s using Single sign-on?

Current systems that make use of Single sign-on include:

• For students

  • College Registration
  • College Course Request
  • Grad Registration

• For Faculty and Staff

  • xMail
  • Staff Access
  • Faculty Access
  • Tracs

As we said, we are working to get more systems online in the coming months, so if there are applications that you think would benefit from SSO, log into myUChicago and send us a note using the “Feedback” link (it’s on the left side of every page). Or you can send us an email at portal-feedback@cticket.uchicago.edu.