Lantronix PremierWave 2050 User Guide - Page 50

Using XML, To Con HTTP Authentication, Using Web Manager, Using the CLI, Line

Page 50 highlights

7: Administration Using XML  Include in your file: The HTTP Server can be configured with many different authentication directives. The authentication is hierarchical in that any URI can be given an authentication directive in order to override a parent URI authentication directive. HTTP Authentication Settings URI Authentication Type Delete Table 7-6 HTTP Authentication Description Enter the URI. The URI must begin with / to refer to the filesystem. Select an HTTP authentication type. The different types offer various levels of security, from the least to most secure:  None: no authentication necessary  Basic: encodes passwords using Base64  Digest: encodes passwords using MD5 When changing the parameters of Digest or SSL/Digest authentication, it is often best to close and reopen the browser to ensure that the it does not attempt to use cached authentication information. Note that SSL by itself does not require a password but all data transferred to and from the HTTP Server is encrypted. There is no real reason to create an authentication directive using None unless you want to override a parent directive that uses some other Authentication Type. Click to delete the existing configuration. To Configure HTTP Authentication Using Web Manager  To configure HTTP authentication, on the Administration page, click HTTP > Authentication. Using the CLI  To enter the HTTP command level: enable -> config -> http Using XML  Include in your file: Line The PremierWave 2050 module contains two serial lines. All lines use standard RS232/RS485 serial ports. All lines can be configured to operate in the following modes:  RS232  RS485 Full Duplex (also compatible with RS-422)  RS485 Half Duplex, with and without termination impedance  All serial settings such as Baud Rate, Parity, Data Bits, etc, apply to these lines. PremierWave® 2050 Enterprise Wi-Fi® IoT Module User Guide 50

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65

7: Administration
PremierWave® 2050 Enterprise Wi-Fi® IoT Module User Guide
50
Using XML
Include in your file:
<statusgroup name="http server">
The HTTP Server can be configured with many different authentication directives. The
authentication is hierarchical in that any URI can be given an authentication directive in order to
override a parent URI authentication directive.
Table 7-6
HTTP Authentication
To Configure HTTP Authentication
Using Web Manager
To configure HTTP authentication, on the
Administration
page, click
HTTP >
Authentication
.
Using the CLI
To enter the HTTP command level:
enable -> config -> http
Using XML
Include in your file:
<configgroup name="http authentication uri">
Line
The PremierWave 2050 module contains two serial lines. All lines use standard RS232/RS485
serial ports. All lines can be configured to operate in the following modes:
RS232
RS485 Full Duplex (also compatible with RS-422)
RS485 Half Duplex, with and without termination impedance
All serial settings such as Baud Rate, Parity, Data Bits, etc, apply to these lines.
HTTP Authentication
Settings
Description
URI
Enter the URI. The URI must begin with / to refer to the filesystem.
Authentication Type
Select an HTTP authentication type. The different types offer various levels of
security, from the least to most secure:
None:
no authentication necessary
Basic:
encodes passwords using Base64
Digest:
encodes passwords using MD5
When changing the parameters of Digest or SSL/Digest authentication, it is
often best to close and reopen the browser to ensure that the it does not
attempt to use cached authentication information.
Note that SSL by itself does not require a password but all data transferred to
and from the HTTP Server is encrypted.
There is no real reason to create an authentication directive using None unless
you want to override a parent directive that uses some other Authentication
Type.
Delete
Click to delete the existing configuration.