2.2 Deploying SaaS Account Management

The SaaS Account Management appliance is tightly integrated with NetIQ Access Manager, but installation and configuration of the appliance are essentially separate. All of the needed configuration for provisioning user accounts to SaaS providers is stored in Access Manager. When the SAM appliance starts up, it communicates with Access Manager and obtains information about all of the applications that have been configured for provisioning. The installation process sets up networking, the root password, and the time server. Access Manager provides all of the other configuration information.

After installation has completed, you must register the appliance with Access Manager. For more information, see Enabling Account Management. You can also set up Syslog remote logging after installation. For more information, see Configuring Remote Logging.

2.2.1 Obtaining SaaS Account Management

You must have purchased SaaS Account Management to access the product in the Customer Center. The activation code is in the Customer Center where you download the software. For more information, see Customer Center Frequently Asked Questions.

To access a full version of SaaS Account Management:

  1. Log in to the Customer Center.

  2. Click Software.

  3. On the Entitled Software tab, click the appropriate version of SaaS Account Management for your environment to download the product.

2.2.2 Deploying the Appliance

The SAM appliance is an Open Virtualization Format (OVF) virtual appliance. You must deploy the appliance to your VMware server.

The appliance must either obtain an IP address through DHCP or have an assigned static IP address. A single *.ovf file is available for the SAM appliance, and the first-boot sequence prompts you to select from DHCP or a static IP address.

To deploy the appliance in a VMware environment:

  1. Download the zipped OVF file from the NetIQ Downloads web page.

  2. Extract or unzip the VMware image to access the OVF file.

  3. Deploy the OVF into your VMware environment and power on the VM.

    • (Conditional) If you have a DHCP server in your environment, deploy the OVF file to a specific ESXi host. For more information, see the VMware documentation.

    • (Conditional) If you do not have a DHCP server in your environment, deploy the OVF file to a VMware vCenter Server.

  4. Follow the on-screen prompts to provide the initial configuration settings for the appliance. These settings include passwords, NTP, and network settings (including whether to use DHCP or a static IP address).

    The initial boot process could take between five and twenty minutes to complete.

    After the first boot process completes, the appliance console displays a screen with Help information, including the URL to access the appliance management console.

  5. Using a browser and the provided URL, log in to the appliance management console and click Account Management to register the SAM appliance and pair it with your Access Manager installation. For more information, see Enabling Account Management.

    IMPORTANT:You must register your SAM appliance before you can provision users. Access Manager does not display any Account Management features until you have registered your SAM appliance.

    Once the registration process has completed, the appliance retrieves any application configuration details. You can then configure SAML2/Account Management applications that are capable of provisioning user accounts to supported SaaS providers.