Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Listed below are basic considerations and practices that must be followed when using an access token:
-
The access token generated must be stored safely.
-
The access token generated must be used to execute all REST Representational State Transfer. REST is a simple and stateless architecture that the web services use for providing interoperability between computer systems on the Internet. In a RESTful web service, requests made to the URI of a resource will elicit a response that may be in XML, HTML, JSON or some other defined format. API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. call. To view the list of APIs managed through HPE Aruba Networking Central, see Viewing Swagger Interface.
-
You must use the same access token to execute an API call without generating new access tokens multiple times. For every API call you must not create new access token.
-
You must save the latest refresh token generated. Once the validity of the access token expires, renew the access token using the saved refresh token.
-
You must refresh the access token when it is invalid or at least once within 15 days so that HPE Aruba Networking Central can honor refreshing the token and does not revoke it.
