Configuration Considerations
Before implementing SSO, there are several business scenarios that should be considered to ensure success.
The following questions should be evaluated before implementing SSO.
|
Question |
Proposed Solution or Recommendation |
|---|---|
|
Are in-house technical skills required on the customer side? |
Technical resources are required to deploy SSO and the knowledge areas include Public/Private Keys, SAML Post (1.1 or 2.0) and encryption algorithms. If there are no internal resources with this expertise, external resources can add extra costs to the project. |
|
What identifier will be used for the user? |
Typically, a company employee ID or email address is used as the SAP Fieldglass username. If an employee ID is used, a buyer code suffix needs to be appended to the end of the username to ensure uniqueness within SAP Fieldglass (ex. “123456789_ABC” where 123456789 is the employee ID and the company code = ABC). |
|
Will users only log in through SSO or will they have SSO and username password access? |
This configuration decision is dependent on the business requirements and may vary based on the user role. |
|
Will there be users that only log in through username password only? |
There may be a need to provide certain users with direct login (username/password) capability. The list of users that require direct login (username/password) access should be supplied before deploying SSO in production. |
|
What is the volume and frequency of changes to the user base? |
As users are added, updated, and removed from the Customer system, corresponding changes must also be made in SAP Fieldglass. If the usernames aren't synchronized, SSO authentication may fail because of mismatches. |
|
How are new users introduced to SAP Fieldglass handled? |
All new users to SAP Fieldglass inherit the SSO setting, as set at the company configuration level. Newly created users won't receive a user invitation if the company is configured for SSO Only. They're allowed to log in for the first time via SSO. No registration is required (as in the username/password email registration process). |