Exchanging Information with the Junos XML Protocol Server
Copyright © 2010, Juniper Networks, Inc.
<request-login>
<username>username</username>
<challenge-response>password</challenge-response>
</request-login>
</rpc>
Interpreting the Authentication Response
After it receives the username and password, the Junos XML protocol server emits the
<authentication-response>
is successful.
Server Response When Authentication Succeeds
If the password is correct, the authentication attempt succeeds and the Junos XML
protocol server emits the following tag sequence:
<rpc-reply xmlns:junos="URL">
<authentication-response>
<status>success</status>
<message>username</message>
<login-name>remote-username</login-name>
</authentication-response>
</rpc-reply>
The
<message>
tag element contains the Junos username under which the connection
is established.
The
tag element contains the username that the client application provided
<login-name>
to an authentication utility such as RADIUS or TACACS+. This tag element appears only
if the username differs from the username contained in the
The Junos XML protocol session begins, as described in "Starting the Junos XML Protocol
Session" on page 38.
Server Response When Authentication Fails
If the password is not correct or the
the authentication attempt fails and the Junos XML protocol server emits the following
tag sequence:
<rpc-reply xmlns:junos="URL">
<authentication-response>
<status>fail</status>
<message>error-message</message>
</authentication-response>
</rpc-reply>
The
string in the
error-message
attempt failed. The Junos XML protocol server emits the
two more times before rejecting the authentication attempt and closing the connection.
The session continues when the client application sends a request to the Junos XML
protocol server. The Junos XML protocol server does not emit any tag elements after
Chapter 3: Controlling the Junos XML Management Protocol Session
tag element to indicate whether the authentication attempt
tag element is otherwise malformed,
<request-login>
tag element explains why the authentication
<message>
tag element.
<message>
<challenge>
tag element up to
45
Need help?
Do you have a question about the JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 and is the answer not in the manual?
Questions and answers