You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 84 Next »

Introduction

This wiki site is offered to assist Cornell web site administrators who are interested in using Shibboleth authentication and authorization technology for access to their website, or to a vendor's website. The Shibboleth Service Provider can usually be used as a replacement for CUWebAuth. The advantage of using Shibboleth is that you can enable access to your site to users from other institutions that are members of the InCommon Federation. 

See the InCommon website for more information and a list of Colleges and Universities that are members.

Shibboleth will not enable people from all colleges and universities to have access to your site, only those that are members of the InCommon Federation. In addition, you can restrict your site to only certain members of InCommon, and only if those members have certain attributes (such as student, faculty, staff, etc.)

Shibboleth is also a popular method for enabling cloud vendor sites to authenticate and authorize Cornell users.

Integrators outside of InCommon who would like to make use of Cornell's Identity Provider may point to the test IDP first and work through any initial issues. When you are ready to move your integration into production, please submit a request at https://shibrequest.cit.cornell.edu to start the process.

In the follow up to a critical security advisory that Shibboleth Consortium released on Feb 27 2018, Identity Provider should begin to insist on the use of XML Encryption going forward. From now on, all the new service provider must provide a certificate for encryption in the metadata.

Cornell IDP Info

Generally, vendors will have the following questions. You can send them a link to this page to get started

Prod IDP: https://shibidp.cit.cornell.edu/idp/shibboleth

Test IDP: https://shibidp-test.cit.cornell.edu/idp/shibboleth

Cornell is the member of InCommon. Cornell's metadata is included in InCommon's metadata. Get Cornell's metadata from InCommon:

http://md.incommon.org/InCommon/InCommon-metadata-idp-only.xml

If you just need the content of Cornell IDP metadata, get it from:

https://shibidp.cit.cornell.edu/idp/shibboleth

If you are integrating test instance of your application, please point it to Cornell IDP test instance. Test IDP's metadata can be accessed from https://shibidp-test.cit.cornell.edu/idp/shibboleth

https://confluence.cornell.edu/display/SHIBBOLETH/IDP+certificate

Prod IDP login URL(POST binding):  https://shibidp.cit.cornell.edu/idp/profile/SAML2/POST/SSO

Prod IDP login URL(Redirect binding): https://shibidp.cit.cornell.edu/idp/profile/SAML2/Redirect/SSO

Test IDP login URL (POST binding): https://shibidp-test.cit.cornell.edu/idp/profile/SAML2/POST/SSO

Test IDP login URL(Redirect binding): https://shibidp-test.cit.cornell.edu/idp/profile/SAML2/Redirect/SSO

No. Our IdP doesn't support logout because our credentials stick around until you close your browser. We usually recommend that you give the user instructions to quit the browser if they want to log out. Recently one of our vendors hooked up their logout button to a page that gives instructions – see example.
No. Weill Medical school has its own Identity Provider. If your application service provider supports multiple Identity Providers, a separate integration request can be sent to Weill Medical IT.
No. Cornell IDP only support Cornell NetID login.
Yes, the Identity Provider is behind the load balancer which provides load balancing and failover.

Currently we release the following public attributes. Other attributes are available but must be configured - please send email to idmgmt@cornell.edu if you don't see the attribute you are looking for.

Majority of Service Providers use Attribute Name In SAML Assertion(value in second column) to map to the attribute in their system, but some service providers use Friendly name in SAML Assertion.

AttributeNameInEnterpriseDirectoryAttribute Name In SAML AssertionAttribute Friendly Name in SAML Assertion
edupersonprimaryaffiliationurn:oid:1.3.6.1.4.1.5923.1.1.1.5edupersonprimaryaffiliation

cn(commonName)

urn:oid:2.5.4.3cn
eduPersonPrincipalName (netid@cornell.edu)urn:oid:1.3.6.1.4.1.5923.1.1.1.6eduPersonPrincipalName
givenName (first name)urn:oid:2.5.4.42givenName
sn(last name)urn:oid:2.5.4.4sn
displayNameurn:oid:2.16.840.1.113730.3.1.241displayName
uid (netid)urn:oid:0.9.2342.19200300.100.1.1uid
eduPersonOrgDNurn:oid:1.3.6.1.4.1.5923.1.1.1.3eduPersonOrgDN
mailurn:oid:0.9.2342.19200300.100.1.3mail
eduPersonAffiliationurn:oid:1.3.6.1.4.1.5923.1.1.1.1eduPersonAffiliation
eduPersonScopedAffiliationurn:oid:1.3.6.1.4.1.5923.1.1.1.9eduPersonScopedAffiliation
eduPersonEntitlementurn:oid:1.3.6.1.4.1.5923.1.1.1.7eduPersonEntitlement

TransientId is the default NameID.

 

Can I get a Cornell NetID to test with?

If you don't already have a Cornell NetID, you might be able to obtain an exception with sponsor NetID. Please talk to the person who is your contact at Cornell, or email idmgmt@cornell.edu.

Do you have a list of sites that are currently using Shibboleth authentication at Cornell?

List of sites currently configured with a Shibboleth SP for authentication and authorization with a Cornell NetID. You can try some of these sites to see what a Shibboleth login looks like. If you are already logged in with your NetID, you may not notice anything except a slight delay. To view the login process in full, exit your browser first to clear your CUWebLogin information.

Service Provider Installation

Installing the Shibboleth Service Provider is a little bit more involved than installing CUWebAuth. We are still developing Cornell specific documentation for installation, and we would appreciate your contributions to this wiki!

There are at least four choices for Service Provider installation.We have experimented with the C version and links to our notes are included here. As we try other versions we will update this site.

Simplesamlphp

This is a popular version in use by many organizations and vendors.

C version, distributed on the Internet2 site

To begin with, you will want to look at the Shibboleth documentation site - we recommend that you install Shibboleth SP 2.4 or later. (Cornell is currently running version 2.3 of the Shibboleth Identity Provider.) You will first want to follow the installation instructions, and then the configuration instructions, and then test with testshib.org - the testshib website has easy instructions that you can follow to do your test. Once you have done that, you can contact us to obtain the Cornell metadata file so that you can authenticate via the Cornell IdP. If you want to work with the InCommon Federation Identity providers, please contact us. (mailto:)

Service Provider Installation how-tos

  • No labels