NetIQ Secure API Manager 1.1 Service Pack 1 Release Notes

Issue: When you integrate Access Manager with Secure API Manager, you must obtain a long-live access token from Access Manager through the Deployment Manager. The token ensure secure communication between Secure API Manager and Access Manager. For more information, see Obtaining a Long-Lived Access Token in the NetIQ Secure API Manager 1.1 Installation Guide.

Workaround: Disable any two-factor authentication methods until after you import the long-live access token. After you import the token, you can enable the two-factor authentication methods.

Issue: Secure API Manager stores the network settings for all of the components in a database on the Database Service component and in the file system on each component. Secure API Manager does not update the entries in the database or the configuration files with the new network settings.

Workaround: If you must change the network settings on an appliance, you must remove the appliance from the Secure API Manager system, restart the remaining components, and then redeploy the appliance with the new network settings. If you have deployed a system in a test environment there is no way to move the system to the production environment. You must redeploy the system in the production environment.

Issue: The components were communicating correctly until someone rebooted one or more of the components, and now the components have stopped communicating with each other.

Solution: Ensure that you restart components in the proper order if you have to shut down or restart a component. For more information, see Restarting Secure API Manager in the NetIQ Secure API Manager 1.1 Administration Guide.

Issue: The CORS options when you create an API do not work properly. For example, if you remove GET, not all of the GET calls are blocked. (Bug 1130572)

Workaround: For this release, do not use the Allow Methods option when implementing CORS.

Issue: If you subscribed to an API through an application and the application has either production or sandbox keys generated, the Authorization: Bearer field on the API Console tab of the Store does not auto-populate with the generated key. (Bug 1128042)

Workaround: When you subscribe to an API in an application, copy the production or sandbox key when you generate the key to enter it in the Authorization: Bearer field when you test the API. For more information, see Managing Subscriptions in the NetIQ Secure API Manager 1.1 API Management Guide.

Issue: If the web browser session for users and administrators changes, Secure API Manager requires that they reauthenticate. This ensures that the database does not get corrupted.

Solution: Users and administrators do not have to reauthenticate if you use sticky sessions on the L4 switch or load balancer. This ensures that the data in Secure API Manager does not get corrupted.

Issue: When you edit a REST API in the Publisher, if the endpoint has a period (.) in its name and you make changes to the Description or Produces field, the Publisher returns a jquery error and does not save the changes. (Bug 1154760)

Workaround: No workaround is currently available for this issue.

Issue: If you edit the Advanced Endpoint Configuration fields in a previously published REST API using strings instead of numbers, the Publisher returns errors when you attempt to save and republish the API. The API is unusable thereafter and you must recreate it. (Bug 1154662)

Solution: Ensure that you use numbers rather than strings in the Advanced Endpoint Configuration fields.

Issue: If you add a certificate for a back-end service during the Publisher stage, it might not immediately propagate to all nodes. (Bug 1156581)

Solution: We recommend that you add all internal certificates using the appliance management console located at https://ip-address-or-dns-name-appliance:9443/vaconfig/certificates.

Issue: When editing the default values for existing Application Tiers, Advanced Throttling Policies, and Subscription Tiers, the following error might appear: Error occurred while executing that action. (Bug 1157606)

Solution: For Application Tiers and Subscription Tiers, this error is a false positive and you can safely ignore it. For Advanced Throttling Policies, it means that you have set up your L4 switch incorrectly. For port 9446 on the gateway, ensure that you have set the connection to be sticky, not round robin. If you do not set the connection to be sticky and you see this error, the database is correctly updated, but the NFS server is not updated and the change will not take effect when throttling.

Issue: You might experience a memory ballooning issue in your VMware environment, particularly if you have over-committed resources.

Solution: If this issue occurs, disable the balloon driver on all of your Secure API Manager appliance VMs. For more information, see VMware Knowledge Base article 1002586.