<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
On Thu, 2013-11-07 at 17:41 -0500, Dmitri Pal wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
On 11/07/2013 12:59 PM, Dean Hunter wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
On Thu, 2013-11-07 at 12:36 -0500, Dmitri Pal wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
On 11/07/2013 12:21 PM, Dean Hunter wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
On Thu, 2013-11-07 at 09:44 +0200, Alexander Bokovoy wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Wed, 06 Nov 2013, Dean Hunter wrote:
<FONT COLOR="#737373">>After building a new VM and configuring the IPA 3.3.2 client, Gnome</FONT>
<FONT COLOR="#737373">>seems to only perform a local log-in until the system is rebooted. SSH</FONT>
<FONT COLOR="#737373">>works with IPA, but not Gnome. Is this correct? Is there anything less</FONT>
<FONT COLOR="#737373">>disruptive than a reboot that I can do?</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
Restart gdm.service?
I'm not sure how gdm handles PAM auth.
</PRE>
</BLOCKQUOTE>
<BR>
I have tried:<BR>
<BLOCKQUOTE>
<TT>ipa-client-install ...</TT><BR>
<TT>systemctl restart gdm.service</TT><BR>
</BLOCKQUOTE>
but the behavior remains the same. The Gnome log in screen accepts the user name, pauses about 25 seconds, then displays the log in screen again without any messages or indication of a problem. This is the same behavior I see when entering an incorrect local user name before configuring IPA.<BR>
<BR>
<BR>
<BR>
<PRE>
_______________________________________________
Freeipa-users mailing list
<A HREF="mailto:Freeipa-users@redhat.com">Freeipa-users@redhat.com</A>
<A HREF="https://www.redhat.com/mailman/listinfo/freeipa-users">https://www.redhat.com/mailman/listinfo/freeipa-users</A>
</PRE>
</BLOCKQUOTE>
Can it be a DIR cache issue and the fact that the directory can't is not created at proper time?<BR>
</BLOCKQUOTE>
<BR>
Which directory, please?<BR>
</BLOCKQUOTE>
<BR>
If you are hitting the DIR cache issue (which I am not sure is the case this is why I asked about AVCs) then the directory we are talking about is /var/run/usr/<uid> <BR>
This directory should be created by kerberos library when it tries to authenticate a user. But it might not be able to since a parent directory /var/run/usr might not be created yet. This is one of the reasons why we decided not to continue the path of DIR cache but switched to using Kernel based ccache.<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BLOCKQUOTE TYPE=CITE>
Do you see any AVCs?<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
Question still stands.<BR>
</BLOCKQUOTE>
<BR>
I see no AVCs:<BR>
<BLOCKQUOTE>
<TT><FONT SIZE="2">[<A HREF="mailto:root@ipa">root@ipa</A> ~]# ausearch --message AVC</FONT></TT><BR>
<TT><FONT SIZE="2"><no matches></FONT></TT><BR>
<TT><FONT SIZE="2">[<A HREF="mailto:root@ipa">root@ipa</A> ~]# </FONT></TT><BR>
<BR>
</BLOCKQUOTE>
I did find this in the man page for nsswitch.conf:<BR>
<BLOCKQUOTE>
<TT><FONT SIZE="2">FILES</FONT></TT><BR>
<TT><FONT SIZE="2"> A service named SERVICE is implemented by a shared object library named</FONT></TT><BR>
<TT><FONT SIZE="2"> libnss_SERVICE.so.X that resides in /lib.</FONT></TT><BR>
<BR>
<TT><FONT SIZE="2"> /etc/nsswitch.conf NSS configuration file.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_compat.so.X implements "compat" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_db.so.X implements "db" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_dns.so.X implements "dns" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_files.so.X implements "files" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_hesiod.so.X implements "hesiod" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_nis.so.X implements "nis" source.</FONT></TT><BR>
<TT><FONT SIZE="2"> /lib/libnss_nisplus.so.X implements "nisplus" source.</FONT></TT><BR>
<BR>
<TT><FONT SIZE="2">NOTES</FONT></TT><BR>
<TT><FONT SIZE="2"> Within each process that uses nsswitch.conf, the entire file is read</FONT></TT><BR>
<TT><FONT SIZE="2"> only once. If the file is later changed, the process will continue</FONT></TT><BR>
<TT><FONT SIZE="2"> using the old configuration.</FONT></TT><BR>
</BLOCKQUOTE>
<BR>
Is this why the default configuration of nsswitch.conf is changing in Fedora 20, as noted on of the preceeding e-mails?<BR>
<BR>
</BODY>
</HTML>