You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to help with support requests related to api keys not being delivered by e-mail (due to spam filtering), we need to adjust our logic for displaying the api keys to administrators. Currently the full keys are not displayed. Here's what I'm thinking in order to make this easier for agency admins to address these support requests themselves, while also maintaining security:
Superuser admins should always be able to view the full keys.
Agency admins can view full API keys for 2 weeks after its creation. I think this should strike a good balance between allowing an ample time for agency admins to deal with initial support while preventing a potentially naughty admin from harvesting a bunch of api keys.
Full API keys will be hidden from agency admins as soon as any roles are added to an API key. Since adding roles is what turns a key from being like any other public key into something that's potentially more sensitive, this seems like a good trigger for hiding it. We'll also assume that the user already has their key if an admin is adding a role to it.
The text was updated successfully, but these errors were encountered:
GUI
added a commit
to NREL/api-umbrella-web
that referenced
this issue
Sep 17, 2015
This is to allow for a bit easier support for admins needing to view the
full api key for users that recently registered (for example, if they
didn't receive their api key). The updated logic is:
- Superuser admins can always view the full api keys.
- Limited admins can view the full api key for 2 weeks after the key was
created.
- If an api key has a role assigned to it by an admin, then the full api
key will only be visible to the admin that created the key for 2
weeks. The full key will be hidden from all other limited admins
immediately.
See 18F/api.data.gov#276
In order to help with support requests related to api keys not being delivered by e-mail (due to spam filtering), we need to adjust our logic for displaying the api keys to administrators. Currently the full keys are not displayed. Here's what I'm thinking in order to make this easier for agency admins to address these support requests themselves, while also maintaining security:
The text was updated successfully, but these errors were encountered: