SonicOSX 7 Device Settings
- SonicOSX 7
- About Device Settings
- Managing SonicWall Licenses
- System Administration
- Configuring the Firewall Name
- Enabling Wireless LAN and IPv6
- Changing the Administrator Name and Password
- Configuring Login Security
- Multiple Administrators Support
- Enabling Enhanced Audit Logging Support
- Configuring the Wireless LAN Controller
- Enabling SonicOSX API and Configuring Authentication Methods
- Enabling GMS Management
- Configuring the Management Interface
- Client Certificate Verification
- Selecting a Language
- Configuring Time Settings
- Managing Certificates
- Administering SNMP
- Firmware Settings
- Restarting the System
- SonicWall Support
Enabling SonicOSX API and Configuring Authentication Methods
You can use SonicOS API as an alternative to the SonicOS Command Line Interface (CLI) for configuring selected functions. To do so, you must first enable SonicOS API. For more information about SonicOS API, see the SonicOS 7.0 API document available at https://www.sonicwall.com/support/technical-documentation/.
To enable SonicOS API and configure client authentication
- Navigate to Device | Settings > Administration.
- Click Audit / SonicOS API.
- In the SONICOS API section, enable SonicOS API.
- Select any of the authentication methods for initial client authentication:
- RFC-7616 HTTP Digest Access authentication
- Select the appropriate digest algorithms: SHA256 (default), MD5
- Integrity protection: Disabled (default), Allowed, or Enforced.
- Session variant (password hashes in place of passwords):Disabled, Allowed (default), or Enforced
- CHAP authentication.
- RFC-2617 HTTP Basic Access authentication
- Public Key Authentication
- RSA modulus (key/cipher size in bits): 2014 is the default.
- RSA padding type: PKCS#1 v1.5 or PKCS#1 v2.0 OAEP
- OAEP hash method: SHA-1, SHA-256, or Other
- OAEP mask (MGF1) method: SHA1, SHA-256, or Other
- Session security using RFC-7616 Digest Access Authentication
- Can hold user passwords received from the client.
- Maximum nonce use: 10 by default
- Two-Factor and Bearer Token Authentication
- RFC-7616 HTTP Digest Access authentication
- Click Accept.
Was This Article Helpful?
Help us to improve our support portal