Project

General

Profile

Control Interface » History » Version 9

Tobias Wich, 09/17/2012 04:34 PM

1 8 Tobias Wich
h1. Client Control Interface
2 1 Moritz Horsch
3 8 Tobias Wich
The Client Control Interface is http based. The webserver of the eCard client is available only under http://localhost:24724.
4 1 Moritz Horsch
5
6 8 Tobias Wich
h2. Activation
7
8
*URL*
9
@http://127.0.0.1:24727/eID-Client@
10
11
*Method*
12
GET
13
14
*Query*
15
| tcTokenURL    | The URL determines where the client can retrieve the TC Token. See TR-03112-7, section 3.2 | Mandatory | 
16
| ifdName       | The ifdName determines the card terminal.|  Optional[1] | 
17
| contextHandle | The contextHandle addresses a specific IFD. | Optional[1] | 
18
| slotHandle    | The slotHandle determines a connected eCard. See TR-03112-6, section 3.2.1. | Optional[1] | 
19
| cardType      | The cardType determines the type of card which must be selected. | Optional[1] |
20
21
*Returns*
22
| 200 OK                    | The refresh address is comprised in the Message Body (Hack for Mac OS Safari). |
23
| 303 See Other             | The Location field in the response should contain the refresh address. |
24
| 400 Bad Request           | Malformed GET request, e.g. parameters are missing. |
25
| 500 Internal Server Error | Other errors. |
26
27
*Content-Types*
28
| text/html | Webpage with user evaluatable content. E.g. error page, manual redirect, ... |
29
30
31
*Description*
32
The interface can be used to start the eID application.
33
34
The parameters ifdName, contextHandle, slotHandle and cardType address a particular eCard, or a type of card.
35
There are three meaningful combinations of the optional parameters:
36
* _none_
37
 Use the fist nPa available. Display a "Please insert nPa" dialog if needed. This is the behaviour of the AusweisApp.
38
* _cardType_
39
 Use the fist card of the specified type which is available. Display a "Please insert <cardType>" dialog if needed.
40
* _ifdName_, _contextHandle_, _slotHandle_
41
 Use exactly the card matching the parameters.
42
43
44
*Notes*
45
46 1 Moritz Horsch
<pre>
47
TODO
48
* What happens if the Client Activator cannot start an application?
49
* What happens if the Client Activator cannot fetch a TC Token from the given TCTokenURL? Should that result in a 400 or 404?
50
</pre>
51
52 8 Tobias Wich
53
54
55
h2. GetStatus[1]
56
57
*URL*
58
@http://127.0.0.1:24727/getStatus@
59
60
*Method*
61
GET
62
63
*Query*
64
| session | The session parameter establishes an event queue for further requests with waitforChange. | Optional | 
65
66
*Returns*
67
| 200 OK                    | Status element (see below). |
68
| 500 Internal Server Error | Errors in the smartcard stack or the webserver. |
69
70
<pre>TODO: define Status element</pre>
71
72
*Content-Types*
73
| text/xml  | The Status element. |
74
| text/html | Error message in case of a 500 status code. |
75
76
77
*Description*
78
The interface can be used to request information about the eID application and its current state.
79
80
81
82
83
h2. WaitForChange
84
85
*URL*
86
@http://127.0.0.1:24727/waitForChange@
87
88
*Method*
89
GET
90
91
*Query*
92 9 Tobias Wich
| session | The session of a previously set up event queue (see [[Client_Activation#GetStatus|GetStatus]]). | Mandatory | 
93 8 Tobias Wich
94
*Returns*
95
| 200 OK                    | StatusChange element (see below). |
96
| 500 Internal Server Error | Errors in the smartcard stack or the webserver. |
97
98
<pre>TODO: define StatusChange element</pre>
99
100
*Content-Types*
101
| text/xml  | The StatusChange element. |
102
| text/html | Error message in case of a 500 status code. |
103
104
105
*Description*
106
The interface can be used to request status change information after an initial GetStatus call.
107
108
109
---
110
111
fn1. Openecard proposal: This parameter/interface is an Open eCard specific extension. It is not part of the official eCard specification.