Description: Indicates the PPP authentication protocol that the device will require a remote peer to use to authenticate itself when the device receives an incoming call from the remote peer. (The device never requires a remote peer to authenticate itself when the device initiates an outgoing call to a remote peer.)

If the value of the ansProfConnProfRequired object is 'connProfNotRequired(2)', the device ignores the actual value of this object and behaves as if it has the value 'authNone(1)'.

If the value of this object is 'authNone(1)', the device will not request the use of an authentication protocol during the Link Establishment phase of PPP link establishment, and the remote peer will not be required to authenticate itself. The device will attempt to match the remote peer's IP address with an instance of the connProfRemIpAddr object. If it successfully matches a connProfileTable entry, the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the connection will be governed by a temporary connection profile created from the values of the following objects:

ansProfIsdnBandwidth ansProfRxRip ansProfTxRip ansProfFilterSetIndex ansProfIdleSeconds ansProfPppMaxRecvUnit ansProfPppLinkCompression ansProfIsdnInForce56K

If the value of this object is 'authPAP(2)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Password Authentication Protocol (PAP) described in RFC 1334. The device will attempt to match the Peer-ID and Password sent by the remote peer in its PAP Authenticate-Request packet to the connProfPppRecvAuthName and connProfPppRecvAuthSecret objects, respectively, in a connProfileTable entry. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected.

If the value of this object is 'authCHAP(3)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Challenge-Handshake Authentication Protocol (CHAP) described in RFC 1334. During the Authentication phase of PPP link establishment, the device will send a CHAP Challenge packet to, and expect a CHAP Response packet from, the remote peer. The ansProfChapChallengeName object indicates the Name that the device will send in its CHAP Challenge packet. The device will attempt to match the Name sent by the remote peer in its CHAP Response packet to the connProfPppRecvAuthName object in a connProfileTable entry. The device use the connProfPppRecvAuthSecret value in each matching connProfileTable entry to attempt to verify the Response Value in the remote peer's CHAP Response packet. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected.