The Access Gateway Throws a 403 Forbidden Page Error for a Resource Protected by a Form Fill Policy
DN Is Added as Provider ID While Installing NMAS SAML Method
Issue in SSL Communication between the Access Gateway and Web Applications
Customized Login Pages Are Missing After Upgrading Access Manager
This issue can happen if a Web server returns a form with a HTTP 403 error code. The Access Gateway, by default, returns its own custom error pages. Hence, this prevents the Form Fill feature to work. To workaround, go to Access Gateway > Advanced Options, enter ProxyErrorOverride off > click OK.
While installing the NMAS SAML method in an external user store, DN is added as Provider ID instead of the metadata URL.
To resolve this issue, perform the following steps:
Log in to the Administration Console which has the external user store.
Go to Roles and Tasks > NMAS > NMAS Login Methods > SAML Assertion > Affiliates.
Select the respective Affiliate and change the provider ID to the identity provider metadata URL. For example, https://www.trunk2.com:8443/nidp/idff/metadata.
After upgrading Access Manager from 3.1 SP4 or 3.1 SP5 to 4.0.x, applications are not accessible. This issue happens when there is any discrepancy between the cipher suites configured for the Access Gateway and the applications protected by this Access Gateway. To workaround this issue, see TID 7016872.
After upgrading Access Manager, you cannot view the customized login JSP pages. This happens when the customized JSP files are not restored or the legacy filesystem directory is not created.
To resolve this issue, see Maintaining Customized JSP Files for Identity Server in the NetIQ Access Manager Appliance 4.2 Installation and Upgrade Guide.