Overview
The Scorecard single sign-on (SSO) option is available for submitters and reviewers only. The SSO does not work for authors added via the author task. Authors will be sent an invitation link to log in directly to Scorecard.
Description
The user account originates in the membership system and that system remains the source of truth. A user must have an account in Personify to log in. The option to create an account in Scorecard is not available when there is an SSO. The create account option should exist on your Personify login page.
Submitter User Experience
- User starts on the Scorecard submitter login page. Typically, clients add introductory text to this page
- User clicks 'Login' button and is redirected to the Personify login page to enter their login credentials
- Personify verifies the login credentials and passes Scorecard an authentication token
- If authentication is successful, the user is redirected back to the Scorecard submitter landing page
- If authentication is unsuccessful, a unique error message will display depending on the type of error
- If it's the first time the user has logged in, a user account is created in Scorecard
- If the user has logged in previously, their profile fields will be updated, if applicable
- Troubleshooting:
- Please submit a ticket to integrationservices@gocadmium.com with username/password and error message. For security, you should request the user temporarily reset their password to ‘Test123’, so they don’t have to provide their actual password.
Reviewer User Experience
- User must first exist in the Scorecard as a reviewer with the reviewer flag set and a member ID filled in. Your Scorecard project manager can assist with importing reviewers with member IDs or can provide a worksheet for you to input member IDs
- User starts on the Scorecard reviewer login page. Typically, clients add introductory text to this page
- User clicks 'Login' and is redirected to the Personify login page to enter their login credentials
- Personify verifies the login credentials and passes Scorecard an authentication token
- If authentication is unsuccessful, a unique error message will display depending on the type of error
- Scorecard checks in the reviewer list to confirm there is a reviewer with that member ID
- If reviewer exists, the user is redirected back to the Scorecard reviewer landing page
- If reviewer does not exist, the user will see a blue screen with an error code
- The user's profile fields are updated upon login, if applicable
- Troubleshooting:
- First, confirm the user is logging in with the member account matching the member ID you’ve assigned in their reviewer profile
- Please submit a ticket to integrationservices@gocadmium.com with username/password and error message. For security, you should request the user temporarily reset their password to ‘Test123’, so they don’t have to provide their actual password.
Required Credentials
We need the following for all integrations (repeat or new):
- PersonifySSOUrl
- ServiceEndpointUrl
- OdataServiceUrl
- RoleServiceUrl
If new, we also need:
- VendorUsername
- VendorPassword
- VendorID
- VendorBlock
- OdataUser
- OdataPassword
Field Mapping
The following fields are mapped from Personify to Scorecard. Fields are updated upon login.
The client should update their Scorecard Settings >>> Users >>> Account Options to ‘Show user profile editor link on landing page’ = ‘No’. The end-user should not edit their profile fields directly in Scorecard, because this data will come from Personify. If the end-user does so, it will be overwritten when the user logs in next.
Personify Field | Scorecard Field | Notes |
FirstName | SubmitterFirstName | Required |
LastName | SubmitterLastName | Required |
NameCredentials | SubmitterCredentials | |
CompanyName | SubmitterOrganization | |
CompanyName | SubmitterAddress1 | |
Address1 | SubmitterAddress2 | |
Address2 | SubmitterAddress3 | |
City | SubmitterCity | |
State | SubmitterState | |
AddressCountryCode | SubmitterCountry | |
PostalCode | SubmitterZip | |
PrimaryPhone | SubmitterTelephoneOffice | |
WorkEmail | SubmitterEmail | Required |
MasterCustomerID | SubmitterMemberID | Required |
DISCLAIMER
For this integration, Cadmium does the development to connect to the third-party system. It is the Customer's responsibility to verify development needs and associated costs with the third-party to allow Cadmium to connect to their system. The required credentials Cadmium needs from the third-party to develop the integration are noted above.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article