Package ubic.gemma.core.security.authentication
@NonNullApi
package ubic.gemma.core.security.authentication
-
ClassDescriptionStrategy used to handle a failed user authentication if it is a ajax style login (ajaxLoginTrue parameter = true) then no redirect happens and a some JSON is sent to the client if the request is not ajax style then the default redirection takes placeStrategy used to handle a successful user authentication if it is a ajax style login (ajaxLoginTrue parameter = true) then no redirect happens and a some JSON is sent to the client if the request is not ajax-style then the default redirection takes placeSpring Security 6
PasswordEncoderthat understands three formats: Legacy SHA-1 + username-as-salt: stored as a bare 40-char hex digest with no prefix, computed asSHA-1(rawPassword + "{" + username + "}")(the exact output of Spring Security 3/4'sShaPasswordEncoderconfigured withReflectionSaltSource(userPropertyToUse="username")— see Gemma's pre-Phase-2applicationContext-security.xml).Extension ofGroupManager.DaoAuthenticationProviderthat understands Gemma's two pre-Phase-2 legacy password formats, both bare 40-char hex SHA-1 with no prefix: Username-salt (post-2009-11-23):SHA-1(rawPassword + "{" + username + "}")— configured via<s:salt-source user-property="username"/>.Creates a security context using manual authentication.Process authentication requests that come from outside a web context.Implementation for Spring Security.Extension ofUserDetailsManager.Exception raised when a user with a given username already exist.Overrides gsec's UserManager to provide Gemma-specific types.Implementation for Spring Security, plus some other handy methods.Read-only implementation of theUserServiceread cluster.Override a few definition from gsec so that we can use Gemma-specific implementations safely.