Login

Current Implementation

Logs in a user in the system. This operation generates a security token that is mandatory in any subsequent API call. The security token identifies a User-Device association. Same user registered in multiple devices will have multiple security tokens.
The login operation also returns some meta-data about the user. For example: organization and facility information, list of active devices for the current user and permissions of the current user.

The currently supported validation scenarios are:

• A valid Tag Id (i.e. NFC) is provided.
• A valid Username and Password are provided.
• A valid User Email and Password are provided.
• A temporal security token (with a life-span of 5 minutes) is requested.

Parameters

Base URL: /validateAccount
Parameters:

API Sample

curl 'http://192.168.2.102:8080/PresentationServices/validateAccount?tagId=poda&deviceId=596a1d880a22eb32&_=1395133673252' -H 'Accept: application/json, text/javascript, */*; q=0.01' -H 'User-Agent: Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36' --compressed

{ "validateAccountFact" : { "accountFact" : { "activeDevices" : [ ],
"facilityId" : "UNC",
"organizationId" : "UNC",
"role" : { "description" : "",
"id" : 2,
"name" : "pod",
"organizationId" : "UNC",
"permissions" : [ { "id" : 54,
"name" : "read_user",
"organizationId" : "UNC"
},
{ "id" : 58,
"name" : "list_patients_from_current_facility"
}
]
},
"token" : "d2360c39-637b-41da-988d-f031db5affbb",
"userId" : "poda",
"username" : "3"
},
"statusFact" : { "success" : true }
} }

Logout

@TODO