org.piangles.gateway.requests.processors

Class LoginRequestProcessor

java.lang.Object

org.piangles.gateway.requests.processors.AbstractRequestProcessor<EndpointReq,EndpointResp>

org.piangles.gateway.requests.processors.AbstractAuthenticationProcessor<LoginRequest,LoginResponse>

org.piangles.gateway.requests.processors.LoginRequestProcessor

All Implemented Interfaces:

RequestProcessor

public final class LoginRequestProcessor
extends AbstractAuthenticationProcessor<LoginRequest,LoginResponse>

Constructor Summary

Constructors

Constructor and Description
LoginRequestProcessor()

Method Summary

Modifier and Type	Method and Description
protected LoginResponse	processRequest(ClientDetails clientDetails, Request request, LoginRequest loginRequest) The user can login in 2 ways.

Methods inherited from class org.piangles.gateway.requests.processors.AbstractAuthenticationProcessor

processGuestSuccessfulLogin, processRegularSuccessfulLogin, shouldValidateSession

Methods inherited from class org.piangles.gateway.requests.processors.AbstractRequestProcessor

getCommunicationPattern, getEndpoint, getEndpointRequestClass, getEndpointResponseClass, getEventProcessingManager, getGatewayDAO, processRequest, setGatewayDAO, setSessionForCurrentThread

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

LoginRequestProcessor

public LoginRequestProcessor()

Method Detail

processRequest

protected LoginResponse processRequest(ClientDetails clientDetails,
                                       Request request,
                                       LoginRequest loginRequest)
                                throws Exception

The user can login in 2 ways. 1. Traditional Approach : LoginId and Password. Also create a new Session and the SessionManagementService should invalidate any old sessions. However the Authentication Service does a few more features to the mix. 2. Enhanced Approach : LoginId and SessionId. In this approach the SessionId is validated with SessionManagementService. However we do need to return AuthResponse and that functionality should not be duplicated here, call needs to be made to Authentication Service. Or we could as well just pass the Request to AuthenticationService and let it deal with the steps there. AuthenticationResponse PasswordMismatch, AccountDisabled, TooManyTries; Also we need to take care of ChangePassword on first login after user is setup. Not sure where that code is to be.

Specified by:

processRequest in class AbstractRequestProcessor<LoginRequest,LoginResponse>

Throws:

Exception