Security Management System (SMS) Unification
Adds support to the System for Cross-domain Identity Management (SCIM) integration to synchronize users provisioned through the SCIM API for access to the Payments Console.
This enhancement eliminates the previous requirement to create application users explicitly in the Payments Application Security Management Console. Users provisioned through SCIM can now access the Payments Console, provided the required roles and branch access are assigned.
Roles required for Payments access must be created in the Core Application Console and enriched with the appropriate function mappings. The factory-shipped ENTITY_ADMIN_ROLE includes the privileges required to create the roles needed for Payments access.
- Separate user creation in the Payments Console is no longer required.
- Separate user enrichment in the Payments Console is no longer required for standard access setup.
- Payments Console enrichment is required only to maintain user-specific preferences, such as date or number formats.
- Separate logins are still required for the Core Application Console and the Payments Console.
- Users can log in through the Core Application Console or directly through the Payments Console, depending on the deployment configuration.
- If the Payments Console is configured as the primary login, user creation in both the Core Application Console and the Payments Console remains mandatory. Users can then navigate to the Core Application Console using the Next Gen UI navigation option from the Payments Console.
Summary
Users provisioned through SCIM or created in the Core Application Console can now access the Payments Console, eliminating the need for separate user creation in the Payments Console. Payments Console enrichment is required only when user-specific preferences or attributes must be maintained.