[thirdparty/systemd.git] / man / pam_systemd.xml

<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
        "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<!--
  This file is part of systemd.

  Copyright 2010 Lennart Poettering

  systemd is free software; you can redistribute it and/or modify it
  under the terms of the GNU Lesser General Public License as published by
  the Free Software Foundation; either version 2.1 of the License, or
  (at your option) any later version.

  systemd is distributed in the hope that it will be useful, but
  WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  Lesser General Public License for more details.

  You should have received a copy of the GNU Lesser General Public License
  along with systemd; If not, see <http://www.gnu.org/licenses/>.
-->

<refentry id="pam_systemd" conditional='HAVE_PAM'>

        <refentryinfo>
                <title>pam_systemd</title>
                <productname>systemd</productname>

                <authorgroup>
                        <author>
                                <contrib>Developer</contrib>
                                <firstname>Lennart</firstname>
                                <surname>Poettering</surname>
                                <email>lennart@poettering.net</email>
                        </author>
                </authorgroup>
        </refentryinfo>

        <refmeta>
                <refentrytitle>pam_systemd</refentrytitle>
                <manvolnum>8</manvolnum>
        </refmeta>

        <refnamediv>
                <refname>pam_systemd</refname>
                <refpurpose>Register user sessions in the systemd login manager</refpurpose>
        </refnamediv>

        <refsynopsisdiv>
                <para><filename>pam_systemd.so</filename></para>
        </refsynopsisdiv>

        <refsect1>
                <title>Description</title>

                <para><command>pam_systemd</command> registers user
                sessions with the systemd login manager
                <citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                and hence the systemd control group hierarchy.</para>

                <para>On login, this module ensures the following:</para>

                <orderedlist>
                        <listitem><para>If it does not exist yet, the
                        user runtime directory
                        <filename>/run/user/$USER</filename> is
                        created and its ownership changed to the user
                        that is logging in.</para></listitem>

                        <listitem><para>The
                        <varname>$XDG_SESSION_ID</varname> environment
                        variable is initialized. If auditing is
                        available and
                        <command>pam_loginuid.so</command> run before
                        this module (which is highly recommended), the
                        variable is initialized from the auditing
                        session id
                        (<filename>/proc/self/sessionid</filename>). Otherwise
                        an independent session counter is
                        used.</para></listitem>

                        <listitem><para>A new systemd scope unit is
                        created for the session. If this is the first
                        concurrent session of the user, an implicit
                        slice below <filename>user.slice</filename> is
                        automatically created and the scope placed in
                        it. In instance of the system service
                        <filename>user@.service</filename> which runs
                        the systemd user manager
                        instance.</para></listitem>
                </orderedlist>

                <para>On logout, this module ensures the following:</para>

                <orderedlist>
                        <listitem><para>If this is enabled, all
                        processes of the session are terminated. If
                        the last concurrent session of a user ends, his
                        user systemd instance will be terminated too,
                        and so will the user's slice
                        unit.</para></listitem>

                        <listitem><para>If the last concurrent session
                        of a user ends, the
                        <varname>$XDG_RUNTIME_DIR</varname> directory
                        and all its contents are removed,
                        too.</para></listitem>
                </orderedlist>

                <para>If the system was not booted up with systemd as
                init system, this module does nothing and immediately
                returns PAM_SUCCESS.</para>

        </refsect1>

        <refsect1>
                <title>Options</title>

                <para>The following options are understood:</para>

                <variablelist class='pam-directives'>

                        <varlistentry>
                                <term><option>class=</option></term>

                                <listitem><para>Takes a string
                                argument which sets the session class.
                                The XDG_SESSION_CLASS environmental variable
                                takes precedence. One of
                                <literal>user</literal>,
                                <literal>greeter</literal>,
                                <literal>lock-screen</literal> or
                                <literal>background</literal>. See
                                <citerefentry><refentrytitle>sd_session_get_class</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                                for details about the session class.</para></listitem>
                        </varlistentry>

                        <varlistentry>
                                <term><option>type=</option></term>

                                <listitem><para>Takes a string
                                argument which sets the session type.
                                The XDG_SESSION_TYPE environmental
                                variable takes precedence. One of
                                <literal>unspecified</literal>,
                                <literal>tty</literal>,
                                <literal>x11</literal> or
                                <literal>wayland</literal>. See
                                <citerefentry><refentrytitle>sd_session_get_type</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                                for details about the session type.</para></listitem>
                        </varlistentry>

                        <varlistentry>
                                <term><option>debug<optional>=</optional></option></term>

                                <listitem><para>Takes an optional
                                boolean argument. If yes or without
                                the argument, the module will log
                                debugging information as it
                                operates.</para></listitem>
                        </varlistentry>
                </variablelist>
        </refsect1>

        <refsect1>
                <title>Module Types Provided</title>

                <para>Only <option>session</option> is provided.</para>
        </refsect1>

        <refsect1>
                <title>Environment</title>

                <para>The following environment variables are set for the processes of the user's session:</para>

                <variablelist class='environment-variables'>
                        <varlistentry>
                                <term><varname>$XDG_SESSION_ID</varname></term>

                                <listitem><para>A session identifier,
                                suitable to be used in filenames. The
                                string itself should be considered
                                opaque, although often it is just the
                                audit session ID as reported by
                                <filename>/proc/self/sessionid</filename>. Each
                                ID will be assigned only once during
                                machine uptime. It may hence be used
                                to uniquely label files or other
                                resources of this
                                session.</para></listitem>
                        </varlistentry>

                        <varlistentry>
                                <term><varname>$XDG_RUNTIME_DIR</varname></term>

                                <listitem><para>Path to a user-private
                                user-writable directory that is bound
                                to the user login time on the
                                machine. It is automatically created
                                the first time a user logs in and
                                removed on his final logout. If a user
                                logs in twice at the same time, both
                                sessions will see the same
                                <varname>$XDG_RUNTIME_DIR</varname>
                                and the same contents. If a user logs
                                in once, then logs out again, and logs
                                in again, the directory contents will
                                have been lost in between, but
                                applications should not rely on this
                                behavior and must be able to deal with
                                stale files. To store session-private
                                data in this directory, the user should
                                include the value of <varname>$XDG_SESSION_ID</varname>
                                in the filename. This directory shall
                                be used for runtime file system
                                objects such as <constant>AF_UNIX</constant> sockets,
                                FIFOs, PID files and similar. It is
                                guaranteed that this directory is
                                local and offers the greatest possible
                                file system feature set the
                                operating system
                                provides.</para></listitem>
                        </varlistentry>
                </variablelist>
        </refsect1>

        <refsect1>
                <title>Example</title>

                <programlisting>#%PAM-1.0
auth       required     pam_unix.so
auth       required     pam_nologin.so
account    required     pam_unix.so
password   required     pam_unix.so
session    required     pam_unix.so
session    required     pam_loginuid.so
session    required     pam_systemd.so</programlisting>
        </refsect1>

        <refsect1>
                <title>See Also</title>
                <para>
                        <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>logind.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>pam.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>pam.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>pam</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>pam_loginuid</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
                        <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
                </para>
        </refsect1>

</refentry>
Commit	Line	Data
160cd5c9 LP	1	<?xml version='1.0'?> <!---nxml--->
	2	<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
	3	"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
	4
	5	<!--
	6	This file is part of systemd.
	7
	8	Copyright 2010 Lennart Poettering
	9
	10	systemd is free software; you can redistribute it and/or modify it
5430f7f2 LP	11	under the terms of the GNU Lesser General Public License as published by
5430f7f2 LP	12	the Free Software Foundation; either version 2.1 of the License, or
160cd5c9 LP	13	(at your option) any later version.
	14
	15	systemd is distributed in the hope that it will be useful, but
	16	WITHOUT ANY WARRANTY; without even the implied warranty of
	17	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
5430f7f2	18	Lesser General Public License for more details.
160cd5c9	19
5430f7f2	20	You should have received a copy of the GNU Lesser General Public License
160cd5c9 LP	21	along with systemd; If not, see <http://www.gnu.org/licenses/>.
	22	-->
	23
47c49034	24	<refentry id="pam_systemd" conditional='HAVE_PAM'>
160cd5c9 LP	25
	26	<refentryinfo>
	27	<title>pam_systemd</title>
	28	<productname>systemd</productname>
	29
	30	<authorgroup>
	31	<author>
	32	<contrib>Developer</contrib>
	33	<firstname>Lennart</firstname>
	34	<surname>Poettering</surname>
	35	<email>lennart@poettering.net</email>
	36	</author>
	37	</authorgroup>
	38	</refentryinfo>
	39
	40	<refmeta>
	41	<refentrytitle>pam_systemd</refentrytitle>
	42	<manvolnum>8</manvolnum>
	43	</refmeta>
	44
	45	<refnamediv>
	46	<refname>pam_systemd</refname>
af3bccd6	47	<refpurpose>Register user sessions in the systemd login manager</refpurpose>
160cd5c9 LP	48	</refnamediv>
	49
	50	<refsynopsisdiv>
e670b166	51	<para><filename>pam_systemd.so</filename></para>
160cd5c9 LP	52	</refsynopsisdiv>
	53
	54	<refsect1>
	55	<title>Description</title>
	56
	57	<para><command>pam_systemd</command> registers user
3fde5f30	58	sessions with the systemd login manager
af3bccd6 LP	59	<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
af3bccd6 LP	60	and hence the systemd control group hierarchy.</para>
160cd5c9 LP	61
	62	<para>On login, this module ensures the following:</para>
	63
	64	<orderedlist>
af62c704	65	<listitem><para>If it does not exist yet, the
160cd5c9	66	user runtime directory
bb29785e	67	<filename>/run/user/$USER</filename> is
160cd5c9 LP	68	created and its ownership changed to the user
	69	that is logging in.</para></listitem>
	70
c36eecdf	71	<listitem><para>The
160cd5c9 LP	72	<varname>$XDG_SESSION_ID</varname> environment
	73	variable is initialized. If auditing is
	74	available and
	75	<command>pam_loginuid.so</command> run before
af62c704	76	this module (which is highly recommended), the
160cd5c9 LP	77	variable is initialized from the auditing
	78	session id
	79	(<filename>/proc/self/sessionid</filename>). Otherwise
	80	an independent session counter is
	81	used.</para></listitem>
	82
3e2f69b7 LP	83	<listitem><para>A new systemd scope unit is
3e2f69b7 LP	84	created for the session. If this is the first
fbce1139	85	concurrent session of the user, an implicit
3e2f69b7 LP	86	slice below <filename>user.slice</filename> is
	87	automatically created and the scope placed in
	88	it. In instance of the system service
fbce1139	89	<filename>user@.service</filename> which runs
3e2f69b7 LP	90	the systemd user manager
3e2f69b7 LP	91	instance.</para></listitem>
160cd5c9 LP	92	</orderedlist>
	93
	94	<para>On logout, this module ensures the following:</para>
	95
	96	<orderedlist>
fbce1139	97	<listitem><para>If this is enabled, all
3e2f69b7	98	processes of the session are terminated. If
fbce1139	99	the last concurrent session of a user ends, his
3e2f69b7 LP	100	user systemd instance will be terminated too,
	101	and so will the user's slice
	102	unit.</para></listitem>
	103
fbce1139 JE	104	<listitem><para>If the last concurrent session
fbce1139 JE	105	of a user ends, the
160cd5c9	106	<varname>$XDG_RUNTIME_DIR</varname> directory
3e2f69b7 LP	107	and all its contents are removed,
3e2f69b7 LP	108	too.</para></listitem>
160cd5c9 LP	109	</orderedlist>
	110
	111	<para>If the system was not booted up with systemd as
af62c704	112	init system, this module does nothing and immediately
160cd5c9 LP	113	returns PAM_SUCCESS.</para>
	114
	115	</refsect1>
	116
	117	<refsect1>
	118	<title>Options</title>
	119
	120	<para>The following options are understood:</para>
	121
ccc9a4f9	122	<variablelist class='pam-directives'>
0e318cad	123
485507b8 MM	124	<varlistentry>
	125	<term><option>class=</option></term>
	126
	127	<listitem><para>Takes a string
	128	argument which sets the session class.
	129	The XDG_SESSION_CLASS environmental variable
49ebd11f LP	130	takes precedence. One of
	131	<literal>user</literal>,
	132	<literal>greeter</literal>,
	133	<literal>lock-screen</literal> or
	134	<literal>background</literal>. See
	135	<citerefentry><refentrytitle>sd_session_get_class</refentrytitle><manvolnum>3</manvolnum></citerefentry>
	136	for details about the session class.</para></listitem>
	137	</varlistentry>
	138
	139	<varlistentry>
	140	<term><option>type=</option></term>
	141
	142	<listitem><para>Takes a string
	143	argument which sets the session type.
	144	The XDG_SESSION_TYPE environmental
	145	variable takes precedence. One of
	146	<literal>unspecified</literal>,
	147	<literal>tty</literal>,
	148	<literal>x11</literal> or
	149	<literal>wayland</literal>. See
	150	<citerefentry><refentrytitle>sd_session_get_type</refentrytitle><manvolnum>3</manvolnum></citerefentry>
	151	for details about the session type.</para></listitem>
485507b8 MM	152	</varlistentry>
485507b8 MM	153
0e318cad	154	<varlistentry>
05a049cc	155	<term><option>debug<optional>=</optional></option></term>
0e318cad	156
05a049cc ZJS	157	<listitem><para>Takes an optional
	158	boolean argument. If yes or without
	159	the argument, the module will log
c36eecdf LP	160	debugging information as it
c36eecdf LP	161	operates.</para></listitem>
0e318cad	162	</varlistentry>
160cd5c9	163	</variablelist>
160cd5c9 LP	164	</refsect1>
	165
	166	<refsect1>
	167	<title>Module Types Provided</title>
	168
	169	<para>Only <option>session</option> is provided.</para>
	170	</refsect1>
	171
	172	<refsect1>
	173	<title>Environment</title>
	174
58474090 LP	175	<para>The following environment variables are set for the processes of the user's session:</para>
58474090 LP	176
ccc9a4f9	177	<variablelist class='environment-variables'>
160cd5c9 LP	178	<varlistentry>
	179	<term><varname>$XDG_SESSION_ID</varname></term>
	180
	181	<listitem><para>A session identifier,
e9dd9f95	182	suitable to be used in filenames. The
160cd5c9 LP	183	string itself should be considered
	184	opaque, although often it is just the
	185	audit session ID as reported by
	186	<filename>/proc/self/sessionid</filename>. Each
	187	ID will be assigned only once during
	188	machine uptime. It may hence be used
	189	to uniquely label files or other
	190	resources of this
	191	session.</para></listitem>
	192	</varlistentry>
	193
	194	<varlistentry>
	195	<term><varname>$XDG_RUNTIME_DIR</varname></term>
	196
	197	<listitem><para>Path to a user-private
	198	user-writable directory that is bound
	199	to the user login time on the
	200	machine. It is automatically created
	201	the first time a user logs in and
	202	removed on his final logout. If a user
	203	logs in twice at the same time, both
	204	sessions will see the same
	205	<varname>$XDG_RUNTIME_DIR</varname>
	206	and the same contents. If a user logs
	207	in once, then logs out again, and logs
	208	in again, the directory contents will
	209	have been lost in between, but
	210	applications should not rely on this
c5315881	211	behavior and must be able to deal with
160cd5c9	212	stale files. To store session-private
e9dd9f95	213	data in this directory, the user should
160cd5c9 LP	214	include the value of <varname>$XDG_SESSION_ID</varname>
	215	in the filename. This directory shall
	216	be used for runtime file system
74d00578	217	objects such as <constant>AF_UNIX</constant> sockets,
160cd5c9 LP	218	FIFOs, PID files and similar. It is
	219	guaranteed that this directory is
	220	local and offers the greatest possible
	221	file system feature set the
	222	operating system
	223	provides.</para></listitem>
	224	</varlistentry>
	225	</variablelist>
	226	</refsect1>
	227
	228	<refsect1>
	229	<title>Example</title>
	230
	231	<programlisting>#%PAM-1.0
	232	auth required pam_unix.so
	233	auth required pam_nologin.so
	234	account required pam_unix.so
	235	password required pam_unix.so
	236	session required pam_unix.so
	237	session required pam_loginuid.so
3e2f69b7	238	session required pam_systemd.so</programlisting>
160cd5c9 LP	239	</refsect1>
	240
	241	<refsect1>
	242	<title>See Also</title>
	243	<para>
af3bccd6 LP	244	<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
	245	<citerefentry><refentrytitle>systemd-logind.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
	246	<citerefentry><refentrytitle>logind.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
	247	<citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
160cd5c9 LP	248	<citerefentry><refentrytitle>pam.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
	249	<citerefentry><refentrytitle>pam.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
	250	<citerefentry><refentrytitle>pam</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
3e2f69b7 LP	251	<citerefentry><refentrytitle>pam_loginuid</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
	252	<citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
	253	<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
	254	<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
160cd5c9 LP	255	</para>
	256	</refsect1>
	257
	258	</refentry>