Ibops protocol Version 0 Working Draft 2 9 March 2015 Technical Committee
Download 202.14 Kb.
|
- Navigate this page:
- 8.5 API – QROpportunity
- 8.5.2 /QROpportunity
- 8.5.3 /enterprise/RegisterSession Opportunity
- 8.5.4 /enterprise/GetsessionStatus
8.4 API – EnrollmentThe Enrollment service is the initial setup for a user. It can work with the already stored initial identities or use an external axiom services for the initial identity. /RegisterAccount Request { name (string): Name of device, info (string, optional): Details information of the device, os (string): OS of the mobile device, externalId (string): Identifier of mobile device (e.g. IMEI), pushRegId (string): Push Notification Registration Id from the specific provider that mobile has, memberExternalId (string):Enteprise integration external identifier (e.g. 'wsj'), loginData (string): JSON with external system login information. It will be used to authenticate against the external system in order to validated the account, deviceFingerprint (string): Device Fingeprint(SHA1 sum), val1 (string), val2 (string) }
clientCertificate (string): Base64 encoded p12 client certificate, clientCertificatePassword (string): Client Certificate Password, id (string): Internal Id of a new registered user profile, loginData (string): Encrypted JSON with profile data which shall be saved on mobile device, credentialsData (string): Encrypted JSON with credential filled in by user, error (ErrorResponse, optional) } ErrorResponse { errorCode (integer, optional), errorDescription (string, optional) } 8.5 API – QROpportunity8.5.1 OverviewOne of the application authentication flows is using QR codes. On the business partner login page, it will display a QR Code image that will contain a Session Opportunity Identifier Mobile Application should start an authentication wizard, which will scan the QR Code, register the session to signal that it is attached to the session and authenticate with his/her biometrics. After biometric authentication, it should send to Backend the result of authentication. 8.5.2 /QROpportunityRequest { name (string): Name of device, info (string, optional): Details information of the device, val1 (string), val2 (string) }
qrImage (string): Base64 encoded QR Code based on a random number, error (ErrorResponse, optional) } ErrorResponse { errorCode (integer, optional), errorDescription (string, optional) } Biometric authentication should send to Backend the result of authentication. Scan Activity Send Authentication Result to backend Register Session Biometric Authentication Figure 13 8.5.3 /enterprise/RegisterSession Opportunity8.5.3.1 InputRequest { memberExternalId (string):External Identifier of enterprise integration (e.g. ‘garanti’), } 8.5.3.2 OutputResponse { sessionQrImage (string): Base64 encoded image with session informations, sessionId (string): Session Internal Identifier, error (ErrorResponse, optional) } ErrorResponse { errorCode (integer, optional), errorDescription (string, optional) } 8.5.4 /enterprise/GetsessionStatus8.5.4.1 InputGetSessionStatusRequest { sessionId (string, optional) } 8.5.4.2 OutputSessionResponse { status (string): Status of session, OPPORTUNITY,CREATED,AUTHENTICATED,FAILED,TIMEOUT,COMPLETED,CANCELED sessionId (string): Session Internal Id, data (Map[string,Object]): Extra values attached to session instance, error (ErrorResponse, optional) } ErrorResponse { errorCode (integer, optional), errorDescription (string, optional) } Directory: committees -> download.php download.php -> Emergency Interoperability Consortium Membership Meeting download.php -> Technical Communicators, Get ready: Here comes Augmented Reality! Rhonda Truitt download.php -> Oasis set tc download.php -> Iepd analyze Requirements Use Cases for edxl situation reporting messages Draft Version 4 download.php -> Technical Committee: oasis transformational Government Framework tc chair download.php -> Reliability of Messages Sent as Responses over an Underlying Request-response Protocol download.php -> Service Component Architecture sca-j common Annotations and apis Specification Version 1 Committee Draft 03 – Rev1 + Issue 127 download.php -> Scenario Two – Hurricane Warning download.php -> Technical Committee: oasis augmented Reality in Information Products (arip) tc chairs download.php -> This is intended as a Non-Standards Track Work Product. [Type the document title] Download 202.14 Kb. Share with your friends:
|