Faculty180 Release Notes: 2019.08.28

When editing SSO ID display error message if no PID exists for user:

Institutional Admin in RPT, FS, or F180, will see an error message when a PID is not associated with a user, so they know what the likely root cause is for not having an SSO ID.

  • For F180 IAs, and for F180 Support Accounts: :
    • When editing a User who has been provisioned with an SSO ID, the IA will see the following error text if a user is not associated with a PID: ’“You cannot add a SSO ID because there is no PID associated with the user you are editing.”
      • User will not see the "Remove SSO ID" button
      • Will not be able to enter any data into the SSO ID fiel
    • When logged into F180 as an Institutional Administrator editing a support account at their institution who has been provisioned with an SSO ID, the above will apply.

Editing SSO ID on Support Accounts: :

Institutional Admin in F180 can modify the SSO ID for a support account user for SSO authentication purposes at any time. F180 Institutional Administrator for a Platform SSO enabled client can click the 'Edit' icon on the Manage Support Accounts page for existing support account users, and they should see the following on the Support Account Form page:

  • the following fields within Section C ‘Login Details’ IF 'Managed by your school (System) is selected:
    • Field Name: “SSO ID”
    • If an institution has CAS configuration for SSO:
      • Instructional text: “Please provide the CAS Identifier”
      • Field Label: “CAS - SSO ID”
      • Field type: Text
      • Required? Yes
      • Red asterisk should display to indicate required field
      • 'Save' AND 'Save and Go Back button cannot be clicked 
  • If an institution has LDAP configuration for SSO:
    • Instructional text: “Please provide the LDAP Identifier”
    • Field Label: “LDAP - SSO ID”
    • Field type: Text
    • Required? Yes
    • Red asterisk should display to indicate required field
    • 'Save' AND 'Save and Go Back button cannot be clicked and opacity should be 40%
  • If an institution has Shibboleth configuration for SSO:
    • Instructional text: “Please provide the Shibboleth identifier, typically EPPN or EmployeeNumber”
    • Field Label: “Shibboleth - SSO ID”
    • Field type: Text
    • Required? Yes
    • Red asterisk should display to indicate required field
    • 'Save' AND 'Save and Go Back button cannot be clicked 
  • If an institution has a legacy SSO type the user will not see this new SSO ID section

Exclude inactive users from push_sso_ids task:

User sending bulk SSO ID information from F180 to Account can exclude inactive users to prevent problems with processing valid additions.

Editing SSO ID on Personal Information section:

An Institutional Administrator in F180 can modify the SSO ID for a user for SSO authentication purposes at any time. F180 as an Institutional Administrator for a Platform SSO enabled institution can click the 'Edit' icon on the Manage Faculty page for existing account users, and will see the following on the Faculty Form page for that user:

  • An additional section under Identification
    • Section Name: “SSO ID”
  • User sees the following fields:
    • If an institution has CAS configuration for SSO:
      • Instructional text: “Please provide the CAS Identifier”
      • Field Label: “CAS - SSO ID”
      • Field type: Text
  • If an institution has LDAP configuration for SSO:
    • Instructional text: “Please provide the LDAP Identifier”
    • Field Label: “LDAP - SSO ID”
    • Field type: Text
  • If an institution has Shibboleth configuration for SSO:
    • Instructional text: “Please provide the Shibboleth identifier, typically EPPN or EmployeeNumber”
    • Field Label: “Shibboleth - SSO ID”
    • Field type: Text
  • If an institution has a legacy SSO type:
    • User should not see this new SSO ID section

Remove SSO ID in F180:

Institutional Admin in F180 can remove the SSO ID for a user to troubleshoot a user who is having login issues with SSO. F180 Institutional Administrator editing a User at their institution who has been provisioned with an SSO ID should see the following on the SSO Identifier tab within the Edit User window 

  • should see the most recent SSO ID that is associated with the user within the SSO ID field
  • a Remove SSO ID button next to the Save button for CAS OR LDAP OR Shibboleth
    • This button cannot be clicked if there is no data within the SSO ID field AND no stored record within ACCOUNT
    • When user clicks this button, the following occurs:
    • A window displays
      • Title: 'Are you sure you want to remove the SSO ID'
      • Instructional Text: ‘Please note that removing an SSO ID is not recommended and may result in the user being unable to log in. Remember, you can always update a user’s SSO ID via the SSO identifier tab.’
      • Clicking X on this window does NOT remove the SSO ID record and returns admin to the Edit User modal with the most recent SSO ID from ACCOUNT displayed
    • User should see a Remove SSO ID button
      • Button text: ‘Remove SSO ID’
      • Clicking this button removes the SSO ID from account AND returns me to the previous scree‌n AND removes the SSO ID record form the screen
    • User should see a Cancel Button
      • Clicking this does NOT remove the SSO ID record NAD returns me to the Edit User modal with the most recent SSO ID from ACCOUNT displayed
  • The above also applies F180 as an Institutional Administrator editing a Support Account User at their institution who has been provisioned with an SSO ID when editing the Support Account Form for the selected user.

Update Missing Pid Error:

We updated the error if a user is missing a pid to "You cannot add a SSO ID because there is no PID associated with the user you are editing. Please reach out to Interfolio for assistance."

Enforce uniqueness per tenant for CAS and LDAP SSO IDs:

User provisioning users will receive an error when attempting to add a duplicate SSO ID, so they do not have multiple users with the same identifier.