head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	97.02.15.18.39.59;	author morgan;	state Exp;
branches;
next	1.1;

1.1
date	97.01.19.17.29.12;	author morgan;	state Exp;
branches;
next	;


desc
@sec 2 -> 3
@


1.2
log
@update for .56
@
text
@.\" Hey Emacs! This file is -*- nroff -*- source.
.\" $Id: pam_authenticate.3,v 1.1 1997/01/19 17:29:12 morgan Exp morgan $
.\" Copyright (c) Andrew G. Morgan 1996-7 <morgan@@parc.power.net>
.TH PAM_AUTHENTICATE 3 "1996 Dec 9" "Linux-PAM 0.55" "App. Programmers' Manual"
.SH NAME

pam_authenticate \- authenticate a user

.SH SYNOPSIS
.B #include <security/pam_appl.h>
.sp
.BI "int pam_authenticate(pam_handle_t " *pamh ", int  " flags ");"
.sp 2
.SH DESCRIPTION
.B pam_authenticate

.br
Use this function to authenticate an applicant user.  It is linked
.I dynamically
to the authentication modules by
.BR Linux-PAM ". "
It is the task of these module to perform such an authentication.  The
specific nature of the authentication is not the concern of the
application.

.br
Following successful completion, the
.BR name
of the authenticated user will be present in the
.BR Linux-PAM
item
.BR PAM_USER ". "
This item may be recovered with a call to
.BR pam_get_item "(3)."

.br
The application developer should note that the modules may request
that the user enter their username via the conversation mechanism (see
.BR pam_start "(3))."
Should this be the case, the user-prompt string can be set via
the
.BR PAM_USER_PROMPT
item (see
.BR pam_set_item "(3))."

.SH "RETURN VALUE"
On success
.BR PAM_SUCCESS
is returned.  All other returns should be considered
authentication failures and will be
.I delayed
by an amount specified with prior calls to
.BR pam_fail_delay "(3). "
Specific failures that demand special attention are the following:
.TP
.B PAM_ABORT
the application should exit immediately. Of course,
.BR pam_end "(3)"
should be called first.

.TP
.B PAM_MAXTRIES
the application has tried too many times to authenticate the
user, authentication should not be attempted again.

.SH ERRORS
May be translated to text with
.BR pam_strerror "(3). "

.SH "CONFORMING TO"
DCE-RFC 86.0, October 1995.

.SH BUGS
.sp 2
none known.

.SH "SEE ALSO"

.BR pam_start "(3), "
.BR pam_get_item "(3) "
.BR pam_fail_delay "(3) "
and
.BR pam_strerror "(3). "

Also, see the three
.BR Linux-PAM
Guides, for
.BR "System administrators" ", "
.BR "module developers" ", "
and
.BR "application developers" ". "
@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
.\" $Id: pam_authenticate.2,v 1.1 1997/01/04 18:24:19 morgan Exp morgan $
d4 1
a4 1
.TH PAM_AUTHENTICATE 2 "1996 Dec 9" "Linux-PAM 0.55" "App. Programmers' Manual"
d34 1
a34 1
.BR pam_get_item "(2)."
d39 1
a39 1
.BR pam_start "(2))."
d44 1
a44 1
.BR pam_set_item "(2))."
d53 1
a53 1
.BR pam_fail_delay "(2). "
d58 1
a58 1
.BR pam_end "(2)"
d68 1
a68 1
.BR pam_strerror "(2). "
d79 3
a81 3
.BR pam_start "(2), "
.BR pam_get_item "(2) "
.BR pam_fail_delay "(2) "
d83 1
a83 1
.BR pam_strerror "(2). "
@
