Project

General

Profile

Actions

Feature #19878

open

Authenticate CAC using CUNYfirst SSO

Added by Raffi Khatchadourian 9 months ago. Updated 7 months ago.

Status:
New
Priority name:
Low
Assignee:
Category name:
Authentication
Target version:
Start date:
2024-03-04
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Does it make sense? It would be nice not to have to maintain a separate password. Thanks!

Actions #1

Updated by Boone Gorges 9 months ago

Thanks for the idea. We've talked about it in the past, but it was much earlier in the CUNY Login rollout, when it wasn't clear what the integration steps would look like. I'll bring it up for discussion with our team.

Actions #2

Updated by Raffi Khatchadourian 9 months ago

Boone Gorges wrote in #note-1:

Thanks for the idea. We've talked about it in the past, but it was much earlier in the CUNY Login rollout, when it wasn't clear what the integration steps would look like. I'll bring it up for discussion with our team.

Thanks, Boone. I'd say that almost all of my separate CUNY passwords are gone, library, etc. At this point, CAC is probably the one separate password I use the most.

Actions #3

Updated by Boone Gorges 9 months ago

Thanks, Raffi. This is helpful context.

As you might imagine, adding an alternative authorization method for an existing application is a pretty thorny business, especially given that we currently have no third-party SSO support at the moment, so we'll need the core infrastructure for account claiming, delinking, etc. But it's something that's been on our roadmap for a while, so we'll have some internal discussions and see how it fits in with our other priorities.

Actions #4

Updated by Boone Gorges 7 months ago

  • Target version set to Future release
Actions

Also available in: Atom PDF