[security-dev] Password Expiration in IDM
Anil.Saldhana at redhat.com
Thu Jan 10 16:58:55 EST 2013
we had overloaded methods as of yesterday.
void updateCredential(Agent agent, Object value);
void updateCredential(Agent agent, Object value, Date effectiveDate,
Majority of the developers will choose the first method and advanced
developers will choose the second.
On 01/10/2013 05:12 AM, Bruno Oliveira wrote:
> Hi Anil, so if I don't want password expiration my method call would
> look like this?
> handler.update(agent, credential, this, null, null)
> Why not overloading methods for it?
> "The measure of a man is what he does with power" - Plato
> Volenti Nihil Difficile
> On Thursday, January 10, 2013 at 4:17 AM, Anil Saldhana wrote:
>> I changed the Password Expiration to a null date for the api when the
>> developer wants infinite expiry passwords. One IDM test was choking.
>> For now, I have set the password expiry to 1500 years if the developer
>> wants infinite expiring passwords.
>> Can you guys take a look? We need better handling when password expiry
>> holds a null date.
More information about the security-dev