J-Web
•
On SRX100, SRX210, SRX220, and SRX240 devices, the commit fails when you configure
an interface under security zone - junos-global. In Junos OS Release 10.4, the junos-global
CLI option is deprecated and is therefore not supported.
NOTE: Junos OS Release 10.3 and earlier releases still support the
junos-global CLI option.
•
The J-Web login page has been updated with the new Juniper Logo and Trademark.
•
URL separation for J-Web and dynamic VPN—This feature prevents the dynamic VPN
users from accessing J-Web accidentally or intentionally. Unique URLs for J-Web and
dynamic VPN add support to the webserver for parsing all the HTTP requests it receives.
The webserver also provides access permission based on the interfaces enabled for
J-Web and dynamic VPN.
•
CLI changes: A new configuration attribute management-url is introduced at the
[edit system services web-management] hierarchy level to control J-Web access
when both J-Web and dynamic VPN are enabled on the same interface. The following
example describes the configuration of the new attribute:
web-management {
traceoptions {
level all;
flag dynamic-vpn;
flag all;
}
management-url my-jweb;
http;
https {
system-generated-certificate;
}
limits {
debug-level 9;
}
session {
session-limit 7;
}
}
•
Enabling only Dynamic VPN: Dynamic VPN must have the configured HTTPS
certificate and the webserver to communicate with the client. Therefore, the
configuration at the [edit system services web-management] hierarchy level required
to start the appweb webserver cannot be deleted or deactivated. To disable J-Web,
the administrator must configure a loopback interface of lo0 for HTTP or HTTPS.
This ensures that the webserver rejects all J-Web access requests.
web-management {
traceoptions {
level all;
flag dynamic-vpn;
flag all;
119Copyright © 2010, Juniper Networks, Inc.
Changes in Default Behavior and Syntax in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
To Next Page
Loading...