Announment : Beta Release of Deploying Access Manager in Docker Container

Deploying Access Manager in Docker Containers


Micro Focus is happy to announce the Beta release of deploying Access Manager as Containers. Access Manager supports Docker for deploying the containers. Access Manager components are delivered as Docker images and are self-sufficient to run on their own.

Access Manager Docker images are optimized to run on Kubernetes, a popular container orchestration engine for Docker. Kubernetes simplifies deploying, running, scaling, and upgrading Access Manager Docker images. The Access Manager Docker images are cloud-native applications and can run in Kubernetes environments deployed on Linux servers and cloud.

Introducing NetIQ Risk Service v2.0

Product Release Announcement: NetIQ Risk Service v2.0


Micro Focus is pleased to announce the availability of NetIQ Risk Service v2.0. This release brings advanced levels of Adaptive Access Management (AAM) to organizations that didn’t have the specialized knowledge or resources to implement it. Through its turnkey integration with ArcSight Interset, NetIQ Risk Service significantly simplifies the adoption of User and Entity Behavioral Analytics (UEBA), enabling organizations to do more than simple step-up authentication. Used together, this solution from Micro Focus raises access management to a higher level of access control intelligence.

Configure Local Firewall on SLES for NAM

Configuring SuSEfirewall2 on SLES 12 for Access Manager


First, create a Firewall Service file that contains the necessary ports to open (the example below assumes the Administration Console and Identity Server run on the same machine - refer to the documentation to adjust as necessary)

> vi /etc/sysconfig/SuSEfirewall2.d/services/netiq-access-manager

Access Manager and Google Chrome v80

Configuring Support for Access Manager on Google Chrome Browser


Google Chrome version 80 onwards introduces a change of how cookies are handled in web browser with the enforcement of SameSite and Secure Cookie configuration. To support this Chrome version with Access Manager, you will need to configure the following options.

Caught Exception at Azure AD Driver Initialization

Identity Manager Azure Active Directory Driver - Caught Exception during Initialization


Situation


The following error is received when attempting to start the Azure AD driver.

DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD_Azure: RESTSubscriptionShim.init()
DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD: Caught exception during REST Channels initialization.
DirXML: [11/30/18 11:46:33.46]: TRACE:  Remote Loader: PublicationShim.init() returned:
DirXML: [11/30/18 11:46:33.46]: TRACE:  <nds dtdversion="4.x" ndsversion="8.x">
    <source>
        <product build="20171120_1044" instance="Azure AD" version="5.0.1.2">Identity Manager Driver for Azure AD and Office 365</product>
        <contact>NetIQ Corporation</contact>
    </source>
    <output>
        <status level="fatal" type="com.novell.nds.dirxml.driver.azure.StatusException"/>
    </output>
</nds>
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Publisher
    Level   = fatal
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Subscriber
    Level   = error
    Message = Fatal error returned from shim

Environment


  • Identity Manager Driver - Azure Active Directory version 5.0.1.2
  • Identity Manager 4.8.0


Resolution


The Application User password being used by the Identity Manager Azure Active Directory driver to authenticate into Azure Active Directory contained a special character in the password.   In this case a < character.


After removing the special character from the password, and saving the new application password for the application user on the driver properties, the driver was able to start successfully.