Security Tool to Test Dual Security Configurations in Lower Environment

Let us consider one example. We have implemented SAML only in Production. SAML is not implemented in our non-production environments. In UAT or Development environments, Business Support and/or IT are required to log in using other users' IDs to replicate incidents, issues, bugs, and test enhancements.

Recently, I designed a solution to prevent single point of failure (SPF) for JMS Store. All Queues across the integration share only one JMS Store as part of the OOB MAS design. JMS store corruption occurs when there is a high volume of messages. Due to SPF, we lose all integration messages.

The solution we developed for SPF involved creating a separate JMS store for each queue. As a result, we have created one queue per external system to separate its traffic.

This solution also involves one POD per JMS store. In environments without SAML, this solution worked well. In production, however, this solution failed, and we encountered some cert/authentication issues, as well as some other unknown login issues.

In order to find the root cause of the problem, we decided to test our SPF solution in lower environments with SAML, but only for select users. In non-production environments, we do not intend to implement SAML for all users. Therefore, we are looking for an internal tool that will allow us to implement dual security for a select group of users.