| Table of Contents |
|---|
Introduction and audience
...
With the vendor’s support or documentation:
Determine if accounts can be provisioned upon login or accounts must be created beforehand.
Some vendors are able to automatically create accounts for any unknown user upon successful login, sometimes called “Just-In-Time” (JIT) provisioning, while other vendors require accounts to be created before users are able to login. For the latter case, arrangements need to be made outside of SSO, such as with an integration by IAM or Banner/Enterprise Solutions, manual account creation, etc.Determine if SAML or CAS will be used.
Some applications only offer one option. If there is a choice, SAML is recommended.Determine if attributes are needed in addition to the attributes released by default.
Complete the PSU Single Sign-On Application Request Form. Provide information to the vendor about PSU’s SSO configuration.
Contact OIT's Identity and Access Management (IAM) team for assistance with the vendor’s forms or questionnaires for implementing SSO.
From the vendor, we need either:The SAML metadata for the Service Provider.
Data required for us to create SAML metadata, viz.:
One or more URLs for Assertion Consumer Service endpoint.
Zero or more public keys/certificates for signing and encryption.
Configure a test instance.
We recommend using a test application instance using our stage environment to get the application working with the SSO testing environment. If possible, keep the test instance to validate future SSO changes before they are moved to production.If troubleshooting is called for, IAM might ask to point to our development environment. Unless your application provides three different environments, do not configure for this environment unless requested.
Note that only our production identity provider has metadata published through InCommon Federation; non-production instances will require manually importing metadata.Configure a production instance.
Use the production information below to configure a production instance of the application.
...
Organization: Portland State University
Contact: PSU IAM Team <oitalert-iamteam-group@pdxiam@pdx.edu>
Member of InCommon: Yes
Identity Provider (IdP): Shibboleth 4.0
...
Odin usernames are occasionally renamed due to special circumstances. Administrators of SSO enabled applications should subscribe to the OIT account rename notification list if tracking username changes is necessary for your application.
...
Often a vendor will request a test account for use in setting up SSO. We do not currently have test accounts in production, but departments can set up affiliate accounts for vendors. Learn more about affiliate accounts.
Frequently asked questions
...
These attributes use a controlled vocabulary from the eduPerson specification. Permissible values are faculty, student, staff, alum, member, affiliate, employee, library-walk-in. Read an explanation of what these values mean as part of the eduPersonAffiliation definition.
The scope of eduPersonScopedAffiliation attributes will usually be “@pdx.edu”. Due to programs such as co-admission with other local institutions, there may be values with other scopes, such as “student@ohsu.edu”; however, anyone eligible for student benefits at PSU will also have “student@pdx.edu”.
...