Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   20652 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

auths(1)			 User Commands			      auths(1)

NAME
       auths - print authorizations granted to a user

SYNOPSIS
       auths [ user ...]

DESCRIPTION
       The auths command prints on standard output the authorizations that you
       or the optionally-specified user or role have been granted.  Authoriza‐
       tions  are  rights  that	 are checked by certain privileged programs to
       determine whether a user may execute restricted functionality.

       Each user may have zero or more authorizations. Authorizations are rep‐
       resented by fully-qualified names, which identify the organization that
       created the authorization and the functionality that it controls.  Fol‐
       lowing  the  Java  convention, the hierarchical components of an autho‐
       rization are separated by dots (.), starting  with  the	reverse	 order
       Internet	 domain name of the creating organization, and ending with the
       specific function within a class of authorizations.

       An asterisk (*) indicates all authorizations in a class.

       A user's authorizations are  looked  up	in  user_attr(4)  and  in  the
       /etc/security/policy.conf file (see policy.conf(4)). Authorizations may
       be  specified  directly	 in   user_attr(4)   or	  indirectly   through
       prof_attr(4).  Authorizations may also be assigned to every user in the
       system directly as default authorizations or indirectly as default pro‐
       files in the /etc/security/policy.conf file.

EXAMPLES
       Example 1: Sample output

       The auths output has the following form:

       example% auths tester01 tester02
       tester01 : solaris.system.date,solaris.jobs.admin
       tester02 : solaris.system.*
       example%

       Notice that there is no space after the comma separating the authoriza‐
       tion names in tester01.

EXIT STATUS
       The following exit values are returned:

       0	Successful completion.

       1	An error occurred.

FILES
       /etc/user_attr

       /etc/security/auth_attr

       /etc/security/policy.conf

       /etc/security/prof_attr

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       ┌─────────────────────────────┬─────────────────────────────┐
       │      ATTRIBUTE TYPE	     │	    ATTRIBUTE VALUE	   │
       ├─────────────────────────────┼─────────────────────────────┤
       │Availability		     │SUNWcsu			   │
       └─────────────────────────────┴─────────────────────────────┘

SEE ALSO
       profiles(1),   roles(1),	  getauthattr(3SECDB),	 auth_attr(4),	  pol‐
       icy.conf(4), prof_attr(4), user_attr(4), attributes(5)

SunOS 5.10			  25 Mar 2004			      auths(1)

Vote for polarhome