In this update, we have added token-based authentication support for Portal and Administrator API's.
- A token is passed with the username and password in JSON. This results in the same response as the login call, except there is an additional field in the response JSON called token. No cookies are sent as part of the response. For example,
http(s)://<IP>:<Port>/amp/portal/login/token (For login to admin, change to /admin instead of /portal). The request is of POST type with the username and password in bodyas JSON format.
- Log out to revoke the token acquired during the API call. For example,
http(s)://<IP><Port>/amp/portal/login/token/revoke?token=<Token that you’ve received from the 1st step>. (For login to admin, change to /admin instead of /portal)
- The token is always passed to the API in Authorization Header value as Bearer <Token>. For example, Authorization: Bearer <Token>
There are two new ways of importing REST resources based on Swagger specifications. They are:
- Using the specification text
- Importing the specification from any location
For more information, see Importing REST API from Swagger.
Log all requests and responses made by your API to a file apimanager-trace.log located in /ColdFusion_2016_install_directory/logs.
For more information, see Request and response logging.
- A new option, Socket Timeout, is added to the list of options when configuring an API Analytics Server. For more information, see API Analytics Server configuration details.
- A new option, Chunked Encoding, is added to the list of options when configuring endpoints of an API. For more information, see Specifying API endpoints.
For a list of bugs fixed in this release, see Bugs fixed.
For a list of known issues in this release, see Known issues.
Method 2: Manual installation
Download the update jar from the location, and enter java -jar hotfix-001-302960.jar in the command prompt. Follow the on-screen instructions.