Hi Rebecca, CSU has implemented SSO for our Concur platform and works well for us. It is a security measure also for CSU. It avoids employees sharing their passwords to pass travel tasks to assistants because they do not want to handle themselves. The employees can assigned travel and expense assistants in their profile to allow others to complete task on their behalf.

WWU does not enforce SSO so admin can log in as other roles such as test users and Expense Admin, for example. SSO does not work for those roles in our system because we don't have profiles for these admin roles in our ERP (at least that's my limited understanding of the logic). But this causes a lot of confusion with our users if they somehow bypass our university's SSO and are asked to login with a Concur user name and password. They usually don't have one or know what it could be and are unable to login without assistance.

Hi Rebecca,
Johns Hopkins uses SSO to access just about everything, so this was a natural extension for our community. It works very well, even the mobile.

At the University of Southern Indiana (USI), we use SSO to access many software tools, including our T&E platform Chrome River. It is seamless whether using a computer/laptop or mobile device. As stated in the comment by Ann Avery, it was also a security measure for USI.

Thanks for all the quick responses so far! Ann and Amy: just want to confirm that you have SSO enforced and not simply as a sign in option, is that correct? The security measure is why we are leaning towards enforcing. Sally: there is a way to enforce SSO for "real" users but not enforce it for test users. Concur can assist with that if WWU is interested.

Thanks, Rebecca!

Hi Rebecca, Correct. SSO is enforced

At the University of Michigan, we have users log in with SSO through our Wolverine Access portal to get to Concur. It's not strictly enforced on the Concur site since Admins (like myself) may need to log into Concur directly from the URL if we are troubleshooting login issues. This configuration has worked well for us and has been in place for some time now.

Hi Rebeca, The University of Miami enforces SSO. The majority of our systems at the University requires SSO, so its one less "password and username" that a user has to remember. I would assume that this would help in lowering administration tasks as it relates to login errors or forgot my password.
The only issue we run into is catering to non-employees/non-students that have to book for themselves and the University reimburses.

The University of Alberta uses SSO. Users have the option of using SSO through our Travel intranet or can log in direct to Concur using their regular web login.

University of Utah uses SSO which is their university username and password login. Sorry no help 🙂

UCLA uses SSO as well. We launched Concur Travel last October 2019 and recently launched Request and Expense in April of 2021

Just something to consider... when registering for the Concur mobile app, they will need their username and will create a PIN (password)… that same username/PIN combo is what's used to login to www.concursolutions.com, so they can still access Concur web application outside of SSO... probably only a risk for those savvy enough to figure that out.

At Tarleton State (Texas A&M system member) we started to use SSO for our concur and Concur app it has helped drastically reduced the need to help people reset their pins for the app and I actually don't even think we have had anyone get locked out since.