[Contents] [Prev] [Next] [Index] [Report an Error]

Interpreting the Authentication Response

After it receives the username and password, the JUNOScript server emits the <authentication-response> tag element to indicate whether the authentication attempt is successful.

If the password is correct, the authentication attempt succeeds and the JUNOScript 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 <login-name> tag element contains the username that the client application provided to an authentication utility such as RADIUS or TACACS+. This tag element appears only if the username differs from the username contained in the <message> tag element.

The JUNOScript session begins, as described in Starting the JUNOScript Session.

If the password is not correct or the <request-login> tag element is otherwise malformed, the authentication attempt fails and the JUNOScript 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 error-message string in the <message> tag element explains why the authentication attempt failed. The JUNOScript server emits the <challenge> tag element up to two more times before rejecting the authentication attempt and closing the connection.

[Contents] [Prev] [Next] [Index] [Report an Error]