Control Interface » History » Version 4
Moritz Horsch, 08/06/2012 12:49 PM
| 1 | 1 | Moritz Horsch | h1. Client Activation |
|---|---|---|---|
| 2 | |||
| 3 | h2. Interface |
||
| 4 | |||
| 5 | 4 | Moritz Horsch | | *URL* |\3. @http://127.0.0.1:24727/eID-Client@ | |
| 6 | | *Method* |\3. GET | |
||
| 7 | |/4. *Query* | tcTokenURL | The URL determines where the client can retrieve the TC Token. See TR-03112-7, section 3.2 | Mandatory | |
||
| 8 | | ifdName | The ifdName determines the card terminal.| Optional; Not specified yet | |
||
| 9 | | contextHandle | | Optional; Not specified yet | |
||
| 10 | | slotHandle | The SlotHandle determines a connected eCard. See TR-03112-6, section 3.2.1. | Optional; Not specified yet | |
||
| 11 | |/4. *Returns* | 200 OK | The refresh address is comprised in the Message Body (Hack for Mac OS Safari). | |
||
| 12 | 3 | Moritz Horsch | | 303 See Other | The Location field in the response should contain the refresh address. | |
| 13 | | 400 Bad Request | Malformed GET request, e.g. parameters are missing. | |
||
| 14 | 1 | Moritz Horsch | | 500 Internal Server Error | | |
| 15 | 4 | Moritz Horsch | |/2. *Content-Types* | text/plain | All content should be encoded in text/plain or text/html. |
| 16 | text/html | |
||
| 17 | | *Notes* | | |
||
| 18 | 1 | Moritz Horsch | |
| 19 | <pre> |
||
| 20 | 3 | Moritz Horsch | TODO |
| 21 | * What happens if the Client Activator cannot start an application? |
||
| 22 | 4 | Moritz Horsch | * What happens if the Client Activator cannot fetch a TC Token from the given TCTokenURL? Should that result in a 400 or 404? |
| 23 | 3 | Moritz Horsch | </pre> |
| 24 | 1 | Moritz Horsch | |
| 25 | 4 | Moritz Horsch | | *URL* |\2. @http://127.0.0.1:24727/status@ | |
| 26 | | *Description* | | |
||
| 27 | 3 | Moritz Horsch | | *Method* |\2. GET | |
| 28 | | *Query* | | | |
||
| 29 | |/4. *Returns* | 200 OK | | |
||
| 30 | 2 | Moritz Horsch | | 400 Bad Request | | |
| 31 | | 406 Not Acceptable | | |
||
| 32 | | 500 Internal Server Error | | |
||
| 33 | 4 | Moritz Horsch | |/3. *Content-Types* | text/html | Should be used for a HTML website with human readable content. | |
| 34 | | application/xml | Should be used to represent a ConnectionHandle in a machine readable XML format. | |
||
| 35 | | application/json | Same as XML but the data should encoded in a JSON format.| |