On 08/30/2012 05:38 AM, george he wrote:
Hello all,
I have free-ipa set up on my lab machines all running Fedora 17.
Today the lab was moved to another building on campus and the IPs have to be
changed.
Now that the IPs are changed, I cannot even run kinit on the ipa-server.
The error
On lör, 2012-08-25 at 23:05 -0500, KodaK wrote:
I've just been informed by my boss's boss's boss that, and I quote
from his ridiculous email:
we cannot use anything other than MS AD for authentication
I've spent months of time and much effort rolling out IPA,
consolidating authentication
Martin Kosek wrote:
On 08/30/2012 05:38 AM, george he wrote:
Hello all,
I have free-ipa set up on my lab machines all running Fedora 17.
Today the lab was moved to another building on campus and the IPs have to be
changed.
Now that the IPs are changed, I cannot even run kinit on the ipa-server.
On 08/29/2012 03:52 PM, Rob Crittenden wrote:
Chris Evich wrote:
On 08/29/2012 11:57 AM, John Dennis wrote:
Thanks for the contribution Chris!
Just as an aside if you know Python you can call the IPA commands
directly and use Python to extract and reformat the data, it might be a
lot simpler
Hi,
Also if its straight into AD Im not aware you can use AD to control a Linux
authentication and authorisation adequately without something like likewise or
centrify. I think the best yiu can do is one group?
regards
Steven Jones
Technical Specialist - Linux RHCE
Victoria University,
Hi,
The biggest thing is really shear control. With the best will in the world AD
is not unix orientated
You can control who logs in to a server and from where, you can control who
gets root remotely (or any other su - *) via IPA's sudo module. You can control
what they can do like
