Resources

Integrating Okta with InCommon: Secure Access in Both Directions

Higher education institutions need to provide secure access to shared research applications without creating identity silos or issuing duplicate credentials. Managing separate connections for every university partner creates administrative overhead and leaves gaps in access controls.

To eliminate manual integrations, IT teams can connect Okta to the InCommon federation using a federation adapter like Cirrus Identity or Shibboleth. The adapter translates between the commercial identity model and the InCommon shared framework. For outbound access, Okta serves as the campus identity provider. Students, faculty, and staff use a single set of credentials and multi-factor authentication to reach third-party InCommon resources directly from the Okta dashboard.

For inbound access, Okta protects the applications your institution hosts. Visiting researchers authenticate through their home institution. A proxy validates the response and passes the trusted identity to Okta, granting access without requiring new credentials.

Download the solution brief to learn how to deploy a federation adapter and establish secure access across the InCommon research and education community.

Topics

  • Datasheet
  • Datasheet
  • IAM
  • Secure Access
  • Education
  • Phishing Resistance
  • Active Directory

Oktaの利用を始めてみませんか?

アイデンティティ施策を推進