|
| 1 | +ietfdb (6.68.0) ietf; urgency=medium |
| 2 | + |
| 3 | + **Ballot position API. Support for API keys.** |
| 4 | + |
| 5 | + This release provides infrastructure to handle API keys and easily |
| 6 | + build API endpoints which use API keys instead of username/password |
| 7 | + login. It also introduces an API endpoint built on this infrastrucure |
| 8 | + in order to let ADs automate posting of their ballot positions (if for |
| 9 | + example they have built their own infrastructure to manage, track, and |
| 10 | + update ballot positions and comments). |
| 11 | + |
| 12 | + Pages to view, create, and disable API keys are available to logged-in |
| 13 | + users. Since the use case for API keys is somewhat different (and possibly |
| 14 | + harder to secure) than the use case for username/password login (they might |
| 15 | + for instance be placed on servers in order to automate operations from the |
| 16 | + server) they have been given some addtional limitations, compared to |
| 17 | + username/password authentication. These are the principles used: |
| 18 | + |
| 19 | + - Each API key is bound to a specific user with a personal profile and |
| 20 | + verified email. |
| 21 | + |
| 22 | + - API keys require an active user -- API keys cannot be used to authorise |
| 23 | + operations if too long a time has passed since the user logged in with |
| 24 | + username and password (this limit is initially set to 30 days). |
| 25 | + |
| 26 | + - API keys can easily be revoked by the owner (and replacement keys |
| 27 | + generated) in order to make it easy to recover from inadvertent |
| 28 | + exposure of a key. |
| 29 | + |
| 30 | + - Each API key is bound to a specific API endpoint. On each use it is |
| 31 | + checked that the API key matches the API endpoint for which it is being |
| 32 | + used. |
| 33 | + |
| 34 | + - API key usage is logged, and users who have active (not disabled) API keys |
| 35 | + will receive a weekly email report for each key showing how many times it |
| 36 | + has been used, and at which time, as a monitoring service. |
| 37 | + |
| 38 | + The release also contains [14404] from rjsparks@nostrum.com: |
| 39 | + Include an explicitly set Responsible ADs email addresses in generated |
| 40 | + aliases when a document has a group. |
| 41 | + |
| 42 | + -- Henrik Levkowetz <henrik@levkowetz.com> 18 Dec 2017 17:58:46 +0000 |
| 43 | + |
1 | 44 | ietfdb (6.67.1) ietf; urgency=medium |
2 | 45 |
|
3 | 46 | **Fixed display of unicode document content** |
|
0 commit comments