How to Add PAP Support to the PPP Configuration Files on Dial-Out Systems

Language:

Note - PPP was removed in the Oracle Solaris 11.4 SRU 24 release.

This procedure uses as examples the PPP configuration files that were introduced in How to Define Communications Over a Serial Line. The procedure configures the dial-out system that belongs to user2, as shown in Example of a PAP Authentication Scenario (Working From Home).

Log in to the dial-out system as superuser.
Modify the /etc/ppp/options file.
The following /etc/ppp/options file contains options for PAP support, which are shown in bold.
```
# cat /etc/ppp/options
lock
name user2
auth
require-pap
```
- name user2 sets user2 as the PAP name of the user on the local system. If the login option is used, the PAP name must be the same as the user's UNIX user name in the password database.
- auth states that the dial-out system must authenticate callers before establishing the link.
  
  Note - This dial-out system demands authentication from its peers, even though most dial-out systems do not make this demand. Either way is acceptable.
- require-pap demands PAP credentials from the peer.
Create an /etc/ppp/peers/peer-name file for the remote system myserver.
The following example shows how to add PAP support to the existing /etc/ppp/peers/myserver file that was created in How to Define the Connection With an Individual Peer.
```
# cat /etc/ppp/peers/myserver
/dev/cua/a
57600
noipdefault
defaultroute
idle 120
user user2
remotename myserver
connect "chat -U 'mypassword' -f /etc/ppp/mychat"
```
The new options in bold add PAP requirements for peer myserver.

user user2
Defines user2 as the user name of the local system.

remotename myserver
Defines myserver as a peer that requires authentication credentials from the local system.

See Also

To test the PAP authentication setup by calling the dial-in server, see How to Call the Dial-In Server.
To learn more about PAP authentication, see Password Authentication Protocol (PAP).