After creating the accelerator, create a new protected resource for your root site.
If the front end of your site is open to the public, then you'll not want any Authentication Procedure. Depending on your needs you may or may not need to create some Authorization rules. We primarily use Authorization Rules to control which Administrators can perform updates. This allows for certain administrators to create and edit users, while leaving the updates to another site administrator. Next we'll need to add some Identity Injections.
These are important as these injections will provide the ability to log-in to WordPress and the information by which a new account can be created. It is recommended that you at least inject the x-cn, x-email, x-firstname, and x-lastname headers. You may choose to inject more if your needs call for it. The username and e-mail are required by WordPress.
The next protected resource will be for our protected content.
Here it is necessary to list all the protected paths. In a MultiSite installation, this list can grow very quickly with at least 2 protected paths per sub-site. You'll want to choose the appropriate Authentication Procedure. This Authentication Procedure is what will allow for the standard Log-in Page to be replaced with the Custom Log-in Page you've designed. After adding the protected paths and selecting the Authentication Procedure, you'll then need to add any authorization rules and set up the Identity Injections as you did on the Root Protected Resource.
After installing the plugin, go to the Settings Menu and enter the necessary headers that you've injected in your Access Manager set up. Here you can also specify the correct Logout URL so that your users can log out of your domain from the WordPress site. You can also choose whether or not you want new users to be created automatically and if so, with what role.
By utilizing both NetIQ Access Manager and the WordPress Header Login plugin, you can take another step towards a seamless and unified experience for your users.