We encountered a strange issue in our customer’s Oracle CTMS application. Our team had configured a customer’s Oracle Siebel CTMS application based on their specific business requirements, including the need for new views for end-users.
The application was working fine for years without any issues until the customer reported that certain views in the application were no longer accessible or visible. When users were trying to navigate to the view, the mouse icon would change to an hourglass for some time and then stop without navigating to the requested view.
Upon further analysis, we identified that the HTTP request made to access the view was not receiving an HTTP 200 OK success status response code. The HTTP 200 OK success status response code indicates that the request has succeeded. The connection attempt was made from the browser, but the server denied the request.
The cause of the issue was due to the latest update to the snort rules updated in the Load Balancer. Snort rules are primarily used for intrusion and vulnerability detection. It uses the rules to identify whether the incoming URL is malicious or not. In this specific case, when navigating to a custom view, the snort rules detected it as a suspicious URL and dropped the connection.
Our IT team identified the snort rule causing the issue. Disabling this rule returned the application to functioning as desired for the custom views.
Do you experience issues with your Siebel applications and infrastructure? If so, reach out to us for help.
