Integration

1. Single Sign-On Usage and Troubleshooting Tips
*Always check the OA’s Salesforce page for more specific information on the type of SSO the OA has before
attempting to troubleshoot.*
Blackboard SSO-
 Single sign-on is determined bya unique number called a PK(ID). If the user’s blackboard account is alreadyconnected to
their Taskstream account,the PK(ID) should appear in the member record under AccountInformation. Always look for
duplicate accounts ifan error message appears for the user.TS-Update can be used to update the PK value if it happens to
be in the system incorrectly or if a lead specifies thatthe value is incorrect.
 If when they click on the link to Taskstream,itsays they do not have an account,but their member record lists a PK(ID), you
will need to use the Single Sign On area in SA to disconnectthatuser. Then, provide login credentials to the user and have
them click on the Taskstream link in Blackboard again. There,they will enter the login credentials. A new PK(ID) will now be
associated with their account.
LTI SSO-
 Single Sign-On is determined by FirstName,LastName,and Email Address. If account is not found, we need to have the
user or school make sure those 3 identifiers in the portal match whatwe have in Taskstream.
SAML SSO-
 Single Sign-On is determined by FirstName,LastName,and Email Address. If account is not found, we need to have the
user or school make sure those 3 identifiers in the portal match whatwe have in Taskstream.Look for duplicate accounts.
Shibboleth SSO-
 Single Sign-On is determined by FirstName,LastName,and Email Address. If account is not found, we need to have the
user or school make sure those 3 identifiers in the portal match whatwe have in Taskstream.
CampusCruiser SSO- (Fresno Pacific University and Western Wyoming CommunityCollege)
 Single Sign-on is determined byPerson ID. If their accountis not being found, confirm the user’s Person ID and update
accordinglyin the member record under AccountInformation (Person ID box).
 If a user has 2 accounts,you will want to make sure the correct Person ID is on the correct accountand make sure the other
accountis inactive. When changing the Person ID on a duplicate account,make sure to add DUP to the beginning ofthe ID.
Always change the wrong account first.
CAS SSO-
 Look at the Person ID and make sure there is not a duplicate account.
TS API (aka Silent Authentication)-(Walden)
 Try running the handshake first.This is done in SA Green.
 For any issues with this,create a bug and email IS-DL. Provide all the details and give the user their login information.Have
them go directly through the website.
Web Service Token SSO-
 Look at the Person ID and make sure there is not a duplicate account.