We are excited to share with you some of our most recent implementations from June and July 2025:
June 2025
- Harvard University - Harvard University Information Technology successfully transitioned all guest accounts from a legacy Identity Provider (IdP) to Cirrus guest accounts. Cirrus linked guest accounts to previously established institutional identifiers and enabled real-time creation of new guest accounts with Cirrus-generated institutional identifiers for authentication and authorization to guest resources.
- National Science Foundation - The National Science Foundation implemented a Cirrus Proxy to enable users to sign in to Research.gov using their home institution credentials from select InCommon-federated Identity Providers.
- Scripps College - Scripps is now accessing applications in the InCommon Federation via the Cirrus Bridge for Entra ID. Using the DNS Add-on feature, they quickly and seamlessly cut over from their Shibboleth server to the Cirrus Bridge for SSO—without requiring any metadata updates.
- Louisiana State University Health Sciences Center (Shreveport) - LSUHS Shreveport uses Entra ID as their primary Identity Provider and integrated the Cirrus Bridge with Entra ID for InCommon multilateral federation consolidate their services within Entra ID. After a short round of testing, they were able to cut over from their Shibboleth identity provider to the CIrrus Bridge for InCommon SPs.
- Smithsonian Institute - The Smithsonian Institute integrated the Cirrus Identity SAML Bridge with Entra ID for InCommon multilateral federation. They decided to temporarily register a second IdP so they could keep both their Shibboleth IdP and the Cirrus Bridge in InCommon during the testing period. Once testing was complete, they removed the old IdP.
- Western Nevada College - Western Nevada College migrated their primary identity provider from Okta to Entra ID and during this implementation they configured a new CIrrus Bridge to allow for InCommon multilateral federation with Entra ID. It was a quick implementation.
- Florida Polytechnic University - Florida Poly utilized the certificate and eduroam services, but is new to InCommon federation. In just two meetings we were able to configure the bridge, register in InCommon, and successfully test.
- North Carolina Central University - NCCU is an InCommon member who migrated to Entra ID and integrated with the Cirrus Bridge with Entra ID in order to reinstate federated services for the university. Since the Bridge was only used for InCommon applications we started with the default R&S profile, but ended up needing to add some additional attributes for a few InCommon SPs.
- Texas A&M University - Texas A&M University (TAMU) implemented a Cirrus solution that allows student-authorized delegates to log in to the TAMU student portal using a guest account to access academic records and other services on behalf of the student.
July 2025 - NOVA Southeastern University - NOVA Southeastern University, new to InCommon, implemented a Cirrus Identity Entra ID Enterprise Cirrus Bridge and registered it with the InCommon Federation to provide NOVA with access to applications in the InCommon Federation. The engagement was completed within a week.
- University of Massachusetts Dartmouth - The University of Massachusetts Dartmouth implemented the Cirrus MFA (One-Time Code) solution to require applicants signing in to UMass Dartmouth services through the university’s Slate tenant (as the identity provider) to use multi-factor authentication.
- UConn Health - UConn Health was interested in InCommon integration to access NIH and other federated applications. In just two weeks they were up and running with the Entra ID Bridge with users logging into federated applications.
- Portland Community College - PCC completed their production implementation of the Entra ID Bridge for their CAS applications. The goal was to retire their Ellucian WS02 Ethos CAS service. PCC had completed a successful pilot earlier in the year with a subset of applications and utilized that knowledge towards a swift implementation of the production Bridge.
- William and Mary - In July, William and Mary completed a large implementation with several phases that began in 2024 to migrate their existing Shibboleth and Apereo CAS infrastructure to Entra ID with the Cirrus Bridge and Log API. They had two separate domains for SAML and CAS applications which were cut over to the Bridge with the DNS Add-On at separate times. William and Mary also utilized the Log API to import logs into their Microsoft Sentinel SIEM tool.
If you’d like to learn more about these solutions or other recent use cases, email sales@cirrusidentity.com and we’d be happy to discuss how we can help!