SSO Integration

Confirm Single Sign On integration is properly configured. For almost all Use Cases, SSO integration means the Members authenticate in a Benefits Admin platform (or other 'Front Door'), and the Member navigates to somewhere on that Platform where they can click through and see the TALON home screen, Shopping experience, or combination of other TALON functionality.

TALON CSM Role

Provide the Client with OAuth2 specifications. Configure the Member Home Page consistent with the Client's desired TALON functionality to access (assuming more than Shopping). Note the Member/Dependent Authentication pattern chosen (often employerGroupId/memberId/dependentId).

Client and/or Client Vendor Role

Decide the specific TALON functionality to be accessed and coordinate Member Home Screen config to support. Note that in many cases, the 'Client' rep to implement SSO may be from the vendor supporting the Platform the Members log into. Implement SSO from the Front Door platform to TALON and test.

Process

Confirmation Steps

  • Confirm desired functionality, including the presence or absence of the TALON 'top bar'. Ensure there is a single 'source of truth'. For example, if the Member is expected to access Claims, Health Plan Cards, or other duplicated information in the Front Door platform, do not include that functionality in the TALON UX (i.e. the Claims widget or Claims hyperlink in the TALON top nav bar).
  • Implement SSO.
  • Test SSO.
  • Document the resulting Member Experience.

Note

No examples are included as each SSO Member Experience is different.