Submitting An Authentication Request - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide
44
See the following sections:
Submitting an Authentication Request on page 44
Interpreting the Authentication Response on page 45

Submitting an Authentication Request

The client application begins the authentication process by emitting an
enclosing the
<request-login>
the <username> tag element to specify the Junos OS account (username) under which
to establish the connection. The account must already be configured on the Junos XML
protocol server device, as described in "Prerequisites for All Access Protocols" on page 27.
You can choose whether or not the application provides the account password as part
of the initial tag sequence.
Providing the Password with the Username
To provide the password along with the username, the application emits the following
tag sequence:
<rpc>
<request-login>
<username>username</username>
<challenge-response>password</challenge-response>
</request-login>
</rpc>
This tag sequence is appropriate if the application automates access to routing, switching,
or security platform information and does not interact with users, or obtains the password
from a user before beginning the authentication process.
Providing Only the Username
To omit the password and specify only the username, the application emits the following
tag sequence:
<rpc>
<request-login>
<username>username</username>
</request-login>
</rpc>
This tag sequence is appropriate if the application does not obtain the password until
the authentication process has already begun. In this case, the Junos XML protocol server
returns the tag element within an
<challenge>
password associated with the username. The tag element encloses the
which the client application can forward to the screen as a prompt for a user. The
echo="no" attribute in the opening
typed by the user does not echo on the screen. The tag sequence is as follows:
<rpc-reply xmlns:junos="URL">
<challenge echo="no">Password:</challenge>
</rpc-reply>
The client application obtains the password and emits the following tag sequence to
forward it to the Junos XML protocol server:
<rpc>
tag element. In the
<request-login>
<rpc-reply>
<challenge> tag specifies that the password string
Copyright © 2010, Juniper Networks, Inc.
tag element
<rpc>
tag element, it encloses
tag element to request the
string,
Password: