*sigh*
Not "Refreshable" and "Destroyable", but "Group" and "UserPrincipal"...
Mike
At 11:25 AM 10/17/2012, Michael StJohns wrote:
>This seems too specific to password based authentication.
>
>How about something like a "PrincipalAttributes" interface to go along with
>Refreshable and Destroy
This seems too specific to password based authentication.
How about something like a "PrincipalAttributes" interface to go along with
Refreshable and Destroyable?
Properties getAttributes();
define a few names: accountExpiration, passwordExpiration, lastLoginTime etc
and their default meanings
The application does not know it, but the KDC does. In this case, if a
user's password is about to expire and he logins to the KDC, the AS-REP
message will include a expiration warning (LastReq data). Currently we
have no way to expose this info to the application. But if we define a
new kind o
If the application know and pass the expiration time to the callback, it
can do the warning in the application level.
If the application does not know the expiration time, I was wondering
that the login context may also not know the time. Does kerberos define
expiration fileds?
I think, it is no
Ping again.
On 08/17/2012 06:18 PM, Weijun Wang wrote:
Hi All
I am working with an OpenJDK contributor (Steve Beaty) recently on this
feature.
We often see messages like "Your password will expire in 5 days. Please
update ASAP" when we login to a system, and we are seeing if we could
also supp
Hi All
I am working with an OpenJDK contributor (Steve Beaty) recently on this
feature.
We often see messages like "Your password will expire in 5 days. Please
update ASAP" when we login to a system, and we are seeing if we could
also support this kind of alert in JAAS.
We first starts wit