After Sentinel 7.3 was released, the Rules and Action options were changed, and it got a little trickier to set up automatic emails to notify security team members about things like login failures. Here’s how you set things up to enable a “Send Email” action to be part of routing actions.
This is an update to my previous Cool Solution: Integrating Salesforce.com and NetIQ Access Manager using SAML2. If you are new to SAML2 and federation, you may still find my first article useful as I endeavored to explain each concept as each configuration step is described. This article is not inclusive, but an update to that article. In the years since it was written, several new features related to SAML have been added to Salesforce.com. I describe some of those here and also add some extra tips along the way.
This is a step-by-step procedure to help customers and partners configure and set up NetIQ Privileged User Manager 2.3.3 with NetIQ Cloud Security Service.
As we know, the eDirectory replication process does not support NAT. The reason is simple: the IP address of each server that conforms the replication ring is stored in the “networkAddress” attribute. Its value cannot change according to the point of view of each server, or the NAT device (if we are talking about servers…
In this step by step guide, you will learn how to configure Sentinel 7 to send emails when a correlation rule named “Example: Bad Login Any User” fires.
Gaurav Vaidya explains how to configure SAML based SSO from NetIQ Access Manager to Novell Service Desk.
If one of your NAM fronted applications is having issues, configure NAM to display a “Maintenance Page” rather than displaying the default NAM error page. This looks much more professional than a 504 Gateway Timeout page.
This document will help you reconfigure eDirectory on an OES Server and restore all OES Services.
This article explains how to configure SecureLogin with DAS and Smart Card to enable Fast User switching in Active Directory mode.
Sometimes, though all installation and configuration of Platform Agent and Sentinel server are successfully done, events may not be sent to Sentinel (Audit Connector) from Platform Agent. One of the main reasons could be the communication port number mismatch…