Task #4488

BII RMBP: Server - Login Access

Added by Tan Lee Yong about 10 years ago. Updated almost 10 years ago.

Status:Work Completed-End life cycleStart date:June 30, 2014
Priority:NormalDue date:
Assignee:M Nurdin Norazan% Done:

100%

Category:Server API DevelopmentSpent time:-
Target version:-

LoginAccessIntegration.docx (13.5 KB) Ngoh Chee Onn, August 06, 2014 10:24

History

#1 Updated by Tan Lee Yong about 10 years ago

  • Project changed from 295 to Maybank BII RMBP
  • Category set to Server API Development

#2 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn about 10 years ago

  • Status changed from New - Begin Life Cycle to Finished Development
  • Assignee changed from Ngoh Chee Onn to M Nurdin Norazan
  • % Done changed from 0 to 100

Hi Nurdin,

Login Access on server side already done, you may call below url to get the response from restful server by using adapter:
i)Module login by enter the username
Path - http://121.121.18.49:9083/bii-rest/service/IBLoginServices/loginPassword
Parameter - userAlias(String), locale(String)
Response - response code(00-success), existing user, image caption, image link, service info bean and etc.
Sample Input - ribuser, en

ii)Module login enter the password(if the user status is unlock need to enter a new password)
Path - http://121.121.18.49:9083/bii-rest/service/IBLoginServices/loginSecQuestion
Parameter - userAlias(String), password(String), existingUser(boolean), channel(Integer), userAgent(String), remoteIPAddress(String), locale(String)
Response - response code(00-success)
Sample Input - "ribuser","testing",true, 2, "mobile", "192.122.21.12", "en"

iii)Module get the link account list and unread Msg Count after successful login
Path - http://121.121.18.49:9083/bii-rest/service/IBLoginServices/loginWelcome
Parameter - userAlias(String), locale(String), channel(Integer), userAgent(String), remoteIPAddress(String), sessionId(String)
Response - response code(00-success), link account list, unread msg count
Sample Input - "ribuser", "en", 2, "mobile", "192.122.21.12", ""

Thank you.

#3 Updated by M Nurdin Norazan about 10 years ago

  • Estimated time set to 2.00

#4 Updated by M Nurdin Norazan about 10 years ago

  • Tracker changed from Task to Bug
  • Status changed from Finished Development to Development / Work In Progress
  • Assignee changed from M Nurdin Norazan to Ngoh Chee Onn
  • % Done changed from 100 to 30
  • Estimated time deleted (2.00)

Correct and incorrect password show no differences. Same output.

#5 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn about 10 years ago

  • Tracker changed from Bug to Task
  • Status changed from Development / Work In Progress to Finished Development
  • Assignee changed from Ngoh Chee Onn to M Nurdin Norazan
  • % Done changed from 30 to 100

Hi Nurdin,

For the BII authentication using openAM to validate it and we didn't has the openAM engine here, that's why all we using for the authentication is mock up, this means what you put on the password field will getting the same response for restful web service.

Thank you.

#6 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn about 10 years ago

Hi nurdin,

Please refer to the attachment document for the latest login integration API.

Thank you.

#7 Updated by M Nurdin Norazan about 10 years ago

  • Tracker changed from Task to Bug
  • Status changed from Finished Development to Development / Work In Progress
  • Assignee changed from M Nurdin Norazan to Ngoh Chee Onn
  • % Done changed from 100 to 0

I got this error message during trigger loginPassword procedure

{
"errors": [
"Runtime: Failed to parse JSON string\nError 404: Not Found"
],
"info": [
],
"isSuccessful": false,
"warnings": [
]
}

#8 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn about 10 years ago

  • Tracker changed from Bug to Task
  • Status changed from Development / Work In Progress to Finished Development
  • Assignee changed from Ngoh Chee Onn to M Nurdin Norazan
  • % Done changed from 0 to 100

I got the response as below.

{
"errorCode": null,
"errorParams": null,
"isSuccessful": true,
"loggerErrorCode": null,
"loggerErrorParams": null,
"loggerResponseCode": "00",
"loggerResponseMessage": null,
"loggerServiceName": null,
"mobileNoFlag": "1",
"responseCode": "00",
"responseHeaders": {
"Content-Language": "en-US",
"Content-Type": "text\/plain",
"Date": "Wed, 06 Aug 2014 03:26:45 GMT",
"Transfer-Encoding": "chunked"
},
"responseMessage": null,
"responseTime": 373,
"serviceName": null,
"sessionId": "",
"statusCode": 201,
"statusReason": "Created",
"totalTime": 373
}

You may try to call it again.

Thank you.

#9 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn about 10 years ago

Hi Nurdin,

For the login welcome module, i already add in a response which is "sessionId".
The sessionId you must use on every API call with userId, means that your request parameter must include "sessionId" and "userId" to validate the user session.
If the user session invalid, you will get the response message "Invalid user session" and logout this user.

For any page didn't call the restful API such as go to the selection module, you need to use below API integration to validate the user session.

function authenticateUserSession() {
path = "bii-rest/service/IBCommonServices/authenticateUserSession";

var input = {
        method : 'post',
        returnedContentType : 'json',
        path : path,
        body:{
            contentType:'application/json; charset=UTF-8',
            content:
                JSON.stringify({
                "userId":1551,
                "sessionId":"20140827112431008650",
                })
            }
    };
    return WL.Server.invokeHttp(input);
}

**This only effective after deploy the war file to websphere.

Thank you.

#10 Updated by Tan Lee Yong almost 10 years ago

  • Status changed from Finished Development to Work Completed-End life cycle

Also available in: Atom PDF