On Wed, May 15, 2013 at 12:43:02PM -0400, Willie Slepecki wrote:
> I have been debugging for a few days trying to figure out why my 13.04
> upgraded machine will not log in to my freeipa server. the only thing i
> find odd is since i updated i began getting these in my sssd.log file
>
> (Tue May 1
Hi,
I am running FreeIPA 3.0 server on Centos 6.4. This provides authentication for
Linux workstations, HPC cluster and file server.
We have some Windows XP machines that need to be able to map a CIFS share, but
these cannot have any clients installed due to being specialist data
acquisition s
I can not find FreeIPA 3.2.0 this morning:
[root@ipa ~]# yum list available bind bind-dyndb-ldap freeipa*
Loaded plugins: langpacks, refresh-packagekit
Available Packages
bind.x86_64 32:9.9.3-0.6.rc2.fc19
updates-testing
bind-dyndb-ldap.x86_64 3.2-1.fc19
upda
Afternoon,
Got a question, I know FreeIPA does not allow anonymous binding so if one
need to create an account to query for such information. I did this during
the sudo setup.
I am trying to get git to use FreeIPA today and I trying to figure where
the bind user should be created under. This got
On Thu, May 16, 2013 at 6:48 PM, William Muriithi <
william.murii...@gmail.com> wrote:
> Afternoon,
>
> Got a question, I know FreeIPA does not allow anonymous binding so if one
> need to create an account to query for such information. I did this during
> the sudo setup.
>
> unless you have chang
On 05/15/2013 08:22 PM, Rob Crittenden wrote:
> Willie Slepecki wrote:
>> Has anyone written a script to debug configuration and connection issues
>> with freeipa clients? Something that can be tailored to a specific nix
>> flavor to say "yes, everything is right, change the permissions on this
>>
On 05/16/2013 09:24 AM, Will Ryder wrote:
> Hi,
>
> I am running FreeIPA 3.0 server on Centos 6.4. This provides authentication
> for Linux workstations, HPC cluster and file server.
>
> We have some Windows XP machines that need to be able to map a CIFS share,
> but these cannot have any clients
hi,
so this is a working version of the script (tested on my test ipa
environment).
You save it as executable and run it as:
$./script ipausername
and you will get the groupnames separated by an empty space a user is
member of.
modify the obvious bits, like kdc.domain.tld, user and password, a
I finally got it to work. What i did was purge the freeipa-client and the
sssd packages. after they were purged i installed them fresh. after
running the install script and pam-config-auth, rebooted and it logged in
perfectly. all i can figure is one of the installation scripts between
going f
