Enhance the user experience for Oracle Banking Digital Experience with single sign-on

The authors want to thank Larry Wong for his contributions to this blog.

A seamless customer experience is critical to customer acquisition, retention, loyalty, and trust. When user registration is complex, sign-on is inconvenient, or updating preferences is cumbersome, your customers likely choose to do business elsewhere. You can address some of these challenges by enabling users to sign-in transparently using single sign-on (SSO). Oracle Digital Banking Experience (OBDX) solution supports an industry standard called Security Assertion Markup Language (SAML), which enables SSO from access management solutions like Oracle Cloud Infrastructure (OCI) Identity and Access Management (IAM).

OBDX smooths out the process

OBDX provides ready-to-go retail, corporate, and Islamic banking experiences, while integrating with existing core banking systems. To provide end customers with an optimal experience, we recommend enabling SSO instead of forcing users to set up yet another username and password that they must remember and manage over time.

This approach allows users to authenticate once and gain access to multiple applications without having to submit credentials for each application. With improving the user experience, enabling SSO through a solution like OCI IAM can help ensure that each app’s specific security and authentication requirements are met. For example, some apps might require multi-factor authentication (MFA) for every visit, while others might want to use a “keep me signed-in” feature to avoid forcing reauthentication at each return visit.

For OBDX specifically, we commonly see requirements for SSO that fall into the following categories:

• Employees: You can manage employee access through a centralized access management solution that adheres to your specific security and audit requirements, while enabling an SSO experience across all your applications.

• Customers: Your customers can log into your banking environment once and access several applications, such as OBDX, for transactional banking, insurance solutions, credit card accounts, relationship portal, and so on. You might require customers to create a set of sign-on credentials specific to your bank or you can choose to allow sign-in from social credentials that are already established elsewhere.

Want to know more?

To learn more about setting up SSO for OBDX, follow our tutorial on enabling SSO for Oracle Banking Digital Experience.

For more information, see the following resources:

• SAML

• Oracle Cloud Infrastructure Identity and Access Management

• Oracle Financial Services Applications