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 by a unique number called a PK(ID). If the user’s blackboard account is already connected to their Taskstream account, the PK(ID) should appear in the member record under Account Information. Always look for duplicate accounts if an 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 that the value is incorrect. If when they click on the link to Taskstream, it says 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 disconnect that user. 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 First Name, Last Name, 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 what we have in Taskstream. SAML SSO- Single Sign-On is determined by First Name, Last Name, 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 what we have in Taskstream. Look for duplicate accounts. Shibboleth SSO- Single Sign-On is determined by First Name, Last Name, 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 what we have in Taskstream. CampusCruiser SSO- (Fresno Pacific University and Western Wyoming Community College) Single Sign-on is determined by Person ID. If their account is not being found, confirm the user’s Person ID and update accordingly in the member record under Account Information (Person ID box). If a user has 2 accounts, you will want to make sure the correct Person ID is on the correct account and make sure the other account is inactive. When changing the Person ID on a duplicate account, make sure to add DUP to the beginning of the ID. Always change the wrong account first.

Integration Document

Download DOCX Report

Upload
taskstream
View
86
Download
0

Embed Size (px)

Citation preview

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 by a unique number called a PK(ID). If the user’s blackboard account is already connected to

their Taskstream account, the PK(ID) should appear in the member record under Account Information. Always look for duplicate accounts if an 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 that the value is incorrect.

If when they click on the link to Taskstream, it says 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 disconnect that user. 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 First Name, Last Name, 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 what we have in Taskstream.

SAML SSO- Single Sign-On is determined by First Name, Last Name, 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 what we have in Taskstream. Look for duplicate accounts.

Shibboleth SSO- Single Sign-On is determined by First Name, Last Name, 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 what we have in Taskstream.

CampusCruiser SSO- (Fresno Pacific University and Western Wyoming Community College) Single Sign-on is determined by Person ID. If their account is not being found, confirm the user’s Person ID and update

accordingly in the member record under Account Information (Person ID box). If a user has 2 accounts, you will want to make sure the correct Person ID is on the correct account and make sure the other

account is inactive. When changing the Person ID on a duplicate account, make sure to add DUP to the beginning of the 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.