GET /user-management-v2/client/radius
FROM API REVISION 6.0
On this resource, you can retrieve the Radius client configuration.
When the Radius client configuration is enabled, the controller will use the Radius server for authentication.
<span class="glyphicon glyphicon-warning-sign small-warning" aria-hidden="true"> The Radius client can be enabled only if the Radius server is disabled.
If you want to apply your configuration in one request, you can use the query-parameter force=true
that will fix the issue for you. But be careful, this can disable something you didn't wanted to.
Used when you are operating a browser without access to the header parameter. This allows you to choose which encoding you want to use for the response:
All these resources can be used according what the resource allows.
To address the raw value of a primitive property, clients append a path segment containing the string $value to the property URL.
To use this query option you need to use the classic resource and add the element name you want to print followed by the query string name.
<span class="warning"><span class="glyphicon glyphicon-warning-sign" aria-hidden="true"> Be careful, the parameter query string is used in the URL and is not like other parameters.
The $select system query option allows clients to request a limited set of properties for each entity.
The value pass in the parameter can be:
*
"(star): This will show all child elements.,
" (comma).If there is no value after the select query option, the parameter will be ignored. All the values that are not specified will not be printed in the response.
If this parameter is not in the request, the Application/Json will be chosen by default.
There are multiple possible values (according the resource):
The first two are the most often used.
Object Name: Radius
Property Name | Type | Description | Method |
---|---|---|---|
AuthenticationPort | Integer | The RADIUS server authentication port number. | GET POST |
AccountingPort | Integer | The RADIUS server accounting port number. | GET POST |
SharedKey | String | This is an encryption key that devices use to encrypt and decrypt user authentication credentials that are sent between devices. The shared key should be a long string of up 32 alphanumeric characters and symbols that would be difficult to guess. For example, he^sg3iq6pg2+gqw@89hsm,wz[ This same key must be copied to the remote RADIUS client. The shared key, can't be less than 16 characters. Dunring a POST the shared key must be encoded in Base64. |
GET POST |
ProxyPort | Integer | This is an internal port used to proxy requests between a local server and a remote server. | GET POST |
Enabled | Boolean | Set this to enable the current mode or not. If set to true this can produce an error according the current configuration. See the description of the resource for more details. |
GET POST |
IpAddress | String | IP address of the RADIUS/OIDC server. This can be the IP address of an ECY series controller that is set as the Server Radius or a suitably-configured RADIUS server on an EC-Net / EC-BOS station. | GET POST |
URL Example: https://0.0.0.0/api/rest/v1/user-management-v2/client/radius
{
"accountingPort": 1820,
"authenticationPort": 1812,
"enabled": false,
"sharedKey": "NV5AIXNLPEFoNEhvJTdfPTxBZEAzXUJRQiZMKkNnO1c=",
"proxyPort": 1814,
"ipAddress": "10.59.82.67"
}
URL Example: https://0.0.0.0/api/rest/v1/user-management-v2/client/radius
<?xml version="1.0" encoding="utf-8"?>
<Radius>
<Enabled>false</Enabled>
<IpAddress>10.59.82.67</IpAddress>
<AuthenticationPort>1812</AuthenticationPort>
<AccountingPort>1820</AccountingPort>
<ProxyPort>1814</ProxyPort>
<SharedKey>NV5AIXNLPEFoNEhvJTdfPTxBZEAzXUJRQiZMKkNnO1c=</SharedKey>
</Radius>