OAuth 2.0 Based Authentication for Remote Web Services
You can use OAuth 2.0 authentication for outgoing HTTP/S requests sent by the device to a Remote Web Service (HTTP/S remote host). The device obtains an access token from the OAuth 2.0 server to authorize each HTTP/S request. Token refresh is handled by the OAuth 2.0 server (i.e., not configurable).
This section describes how to configure OAuth 2.0 authentication for Remote Web Services.
|
➢
|
To configure OAuth 2.0 authentication for Remote Web Services: |
|
1.
|
Configure the OAuth 2.0 server: |
|
b.
|
Add a new row, configuring only the following parameters: |
|
◆
|
'Name' = <any identifiable name> |
|
◆
|
'Server Type' = Standard OAuth 2.0 |
|
◆
|
'Base URL' = <base URL of the OAuth 2.0 server> |
|
◆
|
'Token Endpoint' = <token endpoint URL of OAuth 2.0 server> |
|
◆
|
'Application ID' = <Application (client) ID in OAuth 2.0 server registered for this service> |
|
◆
|
'Secret Key' = <client secret> |
|
◆
|
(Optional) 'Scope' = <scope for access resource permissions> |
|
◆
|
(Optional) 'TLS Context' and 'Verify Certificate' |
|
◆
|
'Network Interface' = <device's local IP network interface for communication with OAuth 2.0 server> |
|
2.
|
Configure the Remote Web Service: |
|
b.
|
Add a new row, and in addition to your specific configuration, assign the OAuth 2.0 server that you configured above (Step 1) to this Remote Web Service, using the 'OAuth 2.0 Server' parameter. |
|
d.
|
Click the HTTP Remote Hosts link located below the table, and then configure the remote HTTP/S host with an address and other settings you require. |