darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-06-23 08:49:46 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
c8a64aeb1908fbb2c3cddf2dd8f8253e7dd08cff
notifications-admin/app/templates/views/api/keys.html

66 lines
2.0 KiB
HTML
Raw Normal View History

Added main nav to logged in pages
2015-12-14 16:53:07 +00:00
{% extends "withnav_template.html" %}
Add pages for create/view/revoke API keys Copying what they’ve done on GOV.UK Pay, we should let users: - generate as many keys as they want - only see the key at time of creation - give keys a name - revoke any key at any time (this should be a one way operation) And based on discussions with @minglis and @servingUpAces, the keys should be used in conjunction with some kind of service ID, which gets encrypted with the key. In other words the secret itself never gets sent over the wire. This commit adds the UI (but not the underlying API integration) for doing the above.
2016-01-19 09:55:13 +00:00
{% from "components/table.html" import list_table, field, hidden_field_heading %}
Use the API key pattern for showing service ID When we show an identifier, like an ID or a key, we have a pattern which adds a ‘copy to clipboard’ button. We weren’t using this pattern for service ID. This commit also moves it under the table, so hopefully people will be less likely to confuse the service ID for an API key when scanning down the page.
2016-04-25 09:48:26 +01:00
{% from "components/api-key.html" import api_key %}
Add an index page for the API integration This commit adds a placeholder page which, for now, just has links to the API keys page and links to the clients. There’s more stuff to come on this page, but this commit just does the reorganising so that it’s easier to review.
2016-09-20 11:34:37 +01:00
{% from "components/page-footer.html" import page_footer %}
Added the shell API keys page [ci skip]
2015-11-30 16:20:45 +00:00
Include service name in page `<title>` In pages specific to a service (e.g. dashboard and sub pages) the title needs to distinguish which service it applies to. This is mainly to give context to screen reader users who could be managing multiple services. Implementing this uses template inheritance: `page_title` includes `per_page_title` includes `service_page_title` ‘GOV.UK Notify’ is inserted into every page title. Pages that set `service_page_title` get the service name inserted too.
2017-02-13 10:45:15 +00:00
{% block service_page_title %}
API keys
Added the shell API keys page [ci skip]
2015-11-30 16:20:45 +00:00
{% endblock %}
Added main nav to logged in pages
2015-12-14 16:53:07 +00:00
{% block maincolumn_content %}
Added the shell API keys page [ci skip]
2015-11-30 16:20:45 +00:00
Make ‘add new’ button line up with <h1> Having changed the layout of the API keys page a bit the vertical misalignment was apparent.
2016-09-20 11:51:09 +01:00
<div class="grid-row">
Use the same pattern as elsewhere for ‘new thing’ On the team and templates pages we have a pattern for adding a new ‘thing’, which is a green button in the top right. This commit changes the API key page to follow the same pattern.
2016-04-25 09:50:17 +01:00
<div class="column-two-thirds">
<h1 class="heading-large">
Add an index page for the API integration This commit adds a placeholder page which, for now, just has links to the API keys page and links to the clients. There’s more stuff to come on this page, but this commit just does the reorganising so that it’s easier to review.
2016-09-20 11:34:37 +01:00
API keys
Use the same pattern as elsewhere for ‘new thing’ On the team and templates pages we have a pattern for adding a new ‘thing’, which is a green button in the top right. This commit changes the API key page to follow the same pattern.
2016-04-25 09:50:17 +01:00
</h1>
</div>
<div class="column-one-third">
Remove bumf from the API keys page
2016-04-29 14:17:34 +01:00
<a href="{{ url_for('.create_api_key', service_id=current_service.id) }}" class="button align-with-heading">Create an API key</a>
Use the same pattern as elsewhere for ‘new thing’ On the team and templates pages we have a pattern for adding a new ‘thing’, which is a green button in the top right. This commit changes the API key page to follow the same pattern.
2016-04-25 09:50:17 +01:00
</div>
</div>
Use 19px not 16px type in more places Making the navigation narrower means that we have more space on every page. So on pages where we had to use 16px type just to fit stuff on the page we can now bump the type size up to something less miserly. This is mainly the team and settings pages. We still need to use 16px on pages which list notifications or previews of spreadsheets, because we’re still trying to fit a lot of information onto these pages, so every little space-saving helps.
2017-03-15 12:50:45 +00:00
<div class="body-copy-table">
{% call(item, row_number) list_table(
keys,
empty_message="You haven’t created any API keys yet",
caption="API keys",
caption_visible=false,
field_headings=[
'API keys',
'Action'
],
field_headings_visible=False
) %}
{% call field() %}
<div class="file-list">
{{ item.name }}
<div class="hint">
{% if item.key_type == 'normal' %}
Live – sends to anyone
{% elif item.key_type == 'team' %}
Team and whitelist – limits who you can send to
{% elif item.key_type == 'test' %}
Test – pretends to send messages
{% endif %}
</div>
</div>
Add pages for create/view/revoke API keys Copying what they’ve done on GOV.UK Pay, we should let users: - generate as many keys as they want - only see the key at time of creation - give keys a name - revoke any key at any time (this should be a one way operation) And based on discussions with @minglis and @servingUpAces, the keys should be used in conjunction with some kind of service ID, which gets encrypted with the key. In other words the secret itself never gets sent over the wire. This commit adds the UI (but not the underlying API integration) for doing the above.
2016-01-19 09:55:13 +00:00
{% endcall %}
Use 19px not 16px type in more places Making the navigation narrower means that we have more space on every page. So on pages where we had to use 16px type just to fit stuff on the page we can now bump the type size up to something less miserly. This is mainly the team and settings pages. We still need to use 16px on pages which list notifications or previews of spreadsheets, because we’re still trying to fit a lot of information onto these pages, so every little space-saving helps.
2017-03-15 12:50:45 +00:00
{% if item.expiry_date %}
{% call field(align='right') %}
<span class='hint'>Revoked {{ item.expiry_date|format_datetime_short }}</span>
{% endcall %}
{% else %}
{% call field(align='right', status='error') %}
<a href='{{ url_for('.revoke_api_key', service_id=current_service.id, key_id=item.id) }}'>Revoke</a>
{% endcall %}
{% endif %}
{% endcall %}
</div>
Add pages for create/view/revoke API keys Copying what they’ve done on GOV.UK Pay, we should let users: - generate as many keys as they want - only see the key at time of creation - give keys a name - revoke any key at any time (this should be a one way operation) And based on discussions with @minglis and @servingUpAces, the keys should be used in conjunction with some kind of service ID, which gets encrypted with the key. In other words the secret itself never gets sent over the wire. This commit adds the UI (but not the underlying API integration) for doing the above.
2016-01-19 09:55:13 +00:00
Add an index page for the API integration This commit adds a placeholder page which, for now, just has links to the API keys page and links to the clients. There’s more stuff to come on this page, but this commit just does the reorganising so that it’s easier to review.
2016-09-20 11:34:37 +01:00
{{ page_footer(
secondary_link=url_for('.api_integration', service_id=current_service.id),
secondary_link_text='Back to API integration'
) }}
Use the API key pattern for showing service ID When we show an identifier, like an ID or a key, we have a pattern which adds a ‘copy to clipboard’ button. We weren’t using this pattern for service ID. This commit also moves it under the table, so hopefully people will be less likely to confuse the service ID for an API key when scanning down the page.
2016-04-25 09:48:26 +01:00
Added the shell API keys page [ci skip]
2015-11-30 16:20:45 +00:00
{% endblock %}
Reference in New Issue Copy Permalink