root is not an ipa managed user so it is purely your pam configuration.
I thought we were trying to figure out why your ipa users are not
handled properly.
--
Thank you,
Dmitri Pal
Sr. Engineering Manager IdM portfolio
Red Hat, Inc.
--
Manage your subscription for the Freeipa-users
On 02/26/2015 01:15 PM, nat...@nathanpeters.com wrote:
On 02/25/2015 04:37 PM, nat...@nathanpeters.com wrote:
It does not seem to recognize the user in the secan attempt but the
first attempt seems to authenticate and then disconnect.
I do not see trace from accounting session but I suspect
On 02/25/2015 04:37 PM, nat...@nathanpeters.com wrote:
It does not seem to recognize the user in the secan attempt but the
first attempt seems to authenticate and then disconnect.
I do not see trace from accounting session but I suspect that your pam
stack does not authorize authenticated
-
From: Dmitri Pal
Sent: Thursday, February 26, 2015 2:12 PM
To: freeipa-users@redhat.com
Subject: Re: [Freeipa-users] [Solaris 10] Cannot login through console or
ssh with ipa users
root is not an ipa managed user so it is purely your pam configuration.
I thought we were trying to figure out why
Nathan Peters wrote:
Yes, we are trying to figure out why IPA users are not being handled
properly however
given that :
1. the method you suggested to troubleshoot my Solaris 10 system, adding
pam_permit.so to the stack, will never work because Solaris does not
include pam_permit.so.
so
On 02/25/2015 02:58 PM, nat...@nathanpeters.com wrote:
I am having trouble logging in with an IPA user on Solaris 10. The
machine is able to correctly initialize tickets using kinit. The issue
appears to be PAM related. I am using FreeIPA 4.1.3.
I have tried to follow the instructions here
It does not seem to recognize the user in the secan attempt but the
first attempt seems to authenticate and then disconnect.
I do not see trace from accounting session but I suspect that your pam
stack does not authorize authenticated user.
Try to allow all authenticated users first. This
It does not seem to recognize the user in the secan attempt but the
first attempt seems to authenticate and then disconnect.
I do not see trace from accounting session but I suspect that your pam
stack does not authorize authenticated user.
Try to allow all authenticated users first. This
On 02/25/2015 04:37 PM, nat...@nathanpeters.com wrote:
It does not seem to recognize the user in the secan attempt but the
first attempt seems to authenticate and then disconnect.
I do not see trace from accounting session but I suspect that your pam
stack does not authorize authenticated user.
