hudson.security
Interface InvalidatableUserDetails

All Superinterfaces:

Serializable, org.acegisecurity.userdetails.UserDetails

All Known Implementing Classes:

HudsonPrivateSecurityRealm.Details

Deprecated. Starting 1.285, Hudson stops persisting Authentication altogether (see NonSerializableSecurityContext), so there's no need to use this mechanism.

public interface InvalidatableUserDetails
extends org.acegisecurity.userdetails.UserDetails

UserDetails that can mark Authentication invalid.

Tomcat persists sessions by using Java serialization (and that includes the security token created by Acegi, which includes this object) and when that happens, the next time the server comes back it will try to deserialize SecurityContext that Acegi puts into HttpSession (which transitively includes UserDetails that can be implemented by Hudson.

Such UserDetails implementation can override the isInvalid() method and return false, so that such SecurityContext will be dropped before the rest of Acegi sees it.

See JENKINS-1482

Author:

Kohsuke Kawaguchi

Method Summary

boolean

isInvalid() Deprecated.

Methods inherited from interface org.acegisecurity.userdetails.UserDetails

getAuthorities, getPassword, getUsername, isAccountNonExpired, isAccountNonLocked, isCredentialsNonExpired, isEnabled

Method Detail

isInvalid

boolean isInvalid()

Deprecated.