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.
Using OAuth 2.0 for Authentication
For secure access to the APIs, the HPE Aruba Networking Central On-Premises API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. Framework plug-in supports the OAuth protocol for authentication and authorization. OAuth 2.0 is a simple and secure authorization framework. It allows applications to acquire an access token for HPE Aruba Networking Central On-Premises through a variety of work flows supported within the OAuth 2.0 specification.
All OAuth 2.0 requests must use the SSL Secure Sockets Layer. SSL is a computer networking protocol for securing connections between network application clients and servers over the Internet. endpoint available at https://apigw-<fqdn> of the HPE Aruba Networking Central instance>/swagger/central.
Access and Refresh Tokens
The access token is a string that identifies a user, an application, or a web page. Applications use the access token to access an API. The access tokens provide temporary and secure access to the APIs.
The access tokens have a limited lifetime. If the application uses web server or user-agent OAuth authentication flows, a refresh token is provided during authorization. Using the refresh token you can get a new access token.
If you are writing a long-running application (web app Short form for application. It generally refers to the application that is downloaded and used on mobile devices. ) or native mobile application, you must refresh the token periodically. For more information, see Refreshing a token.
This section includes the following topics:
