Confirmed users
437
edits
BMO/Meetings/2015-05-26: Difference between revisions
notes from meeting
(Created page with "* Auth delegation & third-party-app session expiration. ** Right now the BAD system will always generate a new API key. Shouldn't we have a mechanism to reuse them, for when...") |
(notes from meeting) |
||
| Line 1: | Line 1: | ||
* Auth delegation & third-party-app session expiration. | * Auth delegation & third-party-app session expiration. | ||
** Right now the BAD system will always generate a new API key. Shouldn't we have a mechanism to reuse them, for when your session expires on the third-party app? | ** Right now the BAD system will always generate a new API key. Shouldn't we have a mechanism to reuse them, for when your session expires on the third-party app? | ||
*** Dylan will implement a feature to re-issue the same api key to a given api key consumer, as long as it isn't obsoleted. Possibly some mechanism for forcing a new key (suggested by dkl) | |||
* Sanitize api_keys from logs like we do with passwords. | |||
** find out if we do this for tokens? | |||
* Push out fix for memory issue with nag warnings tomorrow. | |||