Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Cirrus Identity Bridge #9156

Open
donsizemore opened this issue Nov 10, 2022 · 0 comments
Open

Support Cirrus Identity Bridge #9156

donsizemore opened this issue Nov 10, 2022 · 0 comments

Comments

@donsizemore
Copy link
Contributor

donsizemore commented Nov 10, 2022

An increasing number of institutions are using Microsoft Azure/AD for identity management, and subscribing to Cirrus Identity Bridge to integrate with the InCommon Federation.

Dataverse doesn't appear to properly parse the EPPN provided by Cirrus, and produces a useridentifier in the format user@university.edu. It would help me sleep at night if Dataverse were coded to better parse Cirrus-provided attributes, handle @ symbols in the useridentifier field, or prevent the creation of such useridentifiers in the first place.

There is also the matter of cleaning up existing accounts created under this service, and how these accounts may affect current Dataverse permissions or other operations in the mean time.

Two institutions currently using this service are Western Carolina and the University of Nevada at Las Vegas. East Carolina is preparing to subscribe to Cirrus' offerings.

Possibly related to #5579

@donsizemore donsizemore changed the title Support Okta's Cirrus Identity Bridge Support Okta / Cirrus Identity Bridge Feb 24, 2023
@donsizemore donsizemore changed the title Support Okta / Cirrus Identity Bridge Support Cirrus Identity Bridge Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant