Project

General

Profile

Control Interface » History » Revision 7

Revision 6 (Moritz Horsch, 08/08/2012 09:37 AM) → Revision 7/40 (Moritz Horsch, 08/08/2012 09:54 AM)

h1. Client Activation 

 h2. Interface 

 | *URL*    |\3. @http://127.0.0.1:24727/eID-Client@ | 
 | *Description* |\3. The interface can be used to start the eID application. The parameters ifdName, contextHandle, and slotHandle address a particular eCard. If the parameters are absent, the eID application should ask the user to select an eCard if multiple cards are present. |  
 | *Method*    |\3. GET | 
 |/4. *Query*     | tcTokenURL    | The URL determines where the client can retrieve the TC Token. See TR-03112-7, section 3.2 | Mandatory |  
 | ifdName    | The ifdName determines the card terminal.|    Optional; Not specified yet |  
 | contextHandle    | The contextHandle addresses a specific IFD. |    Optional; Not specified yet |  
 | slotHandle    | The SlotHandle determines a connected eCard. See TR-03112-6, section 3.2.1. | Optional; Not specified yet |  
 |/4. *Returns* | 200 OK |\2. The refresh address is comprised in the Message Body (Hack for Mac OS Safari). | 
 | 303 See Other |\2. The Location field in the response should contain the refresh address. | 
 | 400 Bad Request |\2. Malformed GET request, e.g. parameters are missing. | 
 | 500 Internal Server Error |\2. Other errors. | 
 |/2. *Content-Types* | text/plain |\2. All content should be encoded in text/plain or text/html. | 
 | text/html    |\2. | 
 | *Notes* |\3. | 

 <pre> 
 TODO 
 * What happens if the Client Activator cannot start an application? 
 * What happens if the Client Activator cannot fetch a TC Token from the given TCTokenURL? Should that result in a 400 or 404? 
 </pre> 

 | *URL*    |\2. @http://127.0.0.1:24727/status@ | 
 | *Description* |\2. |  
 | *Method*    |\2. GET | 
 | *Query*     | | |  
 |/4. *Returns* | 200 OK | | 
 | 400 Bad Request | | 
 | 406 Not Acceptable 415 Unsupported Media Type | | 
 | 500 Internal Server Error | | 
 |/3. *Content-Types* | text/html | Should be used for a HTML website with human readable content. | 
 | application/xml | Should be used to represent a ConnectionHandle in a machine readable XML format. | 
 | application/json | Same as XML but the data should encoded in a JSON format.|