Single Sign On (SSO)

Healthcare professionals rely on multiple digital systems daily to perform critical functions such as accessing patient records, verifying prescribed medications, monitoring claims, and treatment workflows. Given the demanding environment, users require seamless authentication mechanisms.

Cross-protocol SSO functionality enables them to securely access necessary systems without the need for repeated authentication. Aikyam Identity Console supports both SSO Inbound and SSO Outbound configurations based on OpenID Connect standards, with extended support for JWT tokens, OpenTokens, and PingFederate for external identity provider integrations.

Understanding inbound Vs outbound SSO Inbound SSO occurs when an external identity provider (IDP) authenticates the user, and the authentication token is then presented to the identity console to authorize access to an internal application. For instance, a user authenticates with a third-party system and seamlessly accesses an internal application (example, Optum Pay) without re-authentication. While Outbound SSO occurs when the Aikyam Identity Console authenticates the user initially and subsequently issues an authentication assertion to an external service to facilitate access without requiring the user to re-authenticate.