Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

<request-login>

Usage

Description

Request authentication by the Junos XML protocol server when using the clear-text or SSL access protocol.

Emitting both the <username> and <challenge-response> tag elements is appropriate if the client application automates access to device information and does not interact with users, or obtains the password from a user before beginning the authentication process.

Emitting only the <username> tag element 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 <challenge> tag element to request the password associated with the account.

Note:

Starting in Junos OS Releases 13.3R7, 14.1R6, 14.2R4, 15.1R2, and 16.1R1, any XML special characters in the username or password elements of a <request-login> RPC request must be escaped. The following five symbols are considered special characters: greater than (>), less than (<), single quote ('), double quote ("), and ampersand (&). Both entity references and character references are acceptable escape sequence formats. For example, &amp; and &#38; are valid representations of an ampersand.

Contents

<challenge-response>

Specify the password for the account named in the <username> tag element. Omit this tag element to have the Junos XML protocol server emit the <challenge> tag element to request the password.
<username>

Name of the user account under which to authenticate with the Junos XML protocol server. The account must already be configured on the device where the Junos XML protocol server is running.

Release Information

XML special characters in the username or password elements must be escaped starting in Junos OS Releases 13.3R7, 14.1R6, 14.2R4, 15.1R2, and 16.1R1.

Related Documentation