On 03/21/2016 06:56 PM, Rob Crittenden wrote:
> Bob wrote:
>> If each IPA server tracks time of last auth independently, then one ipa
>> server might disable an inactive account. But that account might be
>> active on another servers. In a fail over case where the server that
>> that account normal
Bob wrote:
If each IPA server tracks time of last auth independently, then one ipa
server might disable an inactive account. But that account might be
active on another servers. In a fail over case where the server that
that account normally uses is down, the user would not have a usable
account.
If each IPA server tracks time of last auth independently, then one ipa
server might disable an inactive account. But that account might be active
on another servers. In a fail over case where the server that that account
normally uses is down, the user would not have a usable account.
Is it possi
Bob wrote:
We currently have 18 master ODSEE servers that we use to provide authentication
services to both Redhat, SuSE, and Solaris systems. We are looking to add IPA
servers to
environment.
We have a requirement to track time of last authentication. With ODSEE, time
of last authentication
We currently have 18 master ODSEE servers that we use to provide
authentication services to both Redhat, SuSE, and Solaris systems. We
are looking to add IPA servers to environment.
We have a requirement to track time of last authentication. With
ODSEE, time of last authentication tracking is ena
