Open holmes-ra opened 11 years ago
confirmed that Yapeal does disable key if it was deleted. Still need to test if it disabled with expiration / vcode change. As of commit 90b83ddc5 preliminary support has been added by adding a refresh button to key grid, which will simply set isActive
to 1
.
TODO: validate that key is legit before setting isActive. Also show if activeAPIMask
equals accessMask
from api key info table (new relation has also been added to registered key model - info
- which will link to this table). If not equal (if user changes it on EVE-O site), set row class to warning, and when refresh button is clicked set activeAPIMask
to info.accessMask
Tested: key is disabled if expired or vCode changes on CCPs side
Need to test/handle key type switching (account / character / corp)
Original question: What happens when users delete/modify keys on EVE Online site?
Need to test if Yapeal handles this automatically. I will still probably need to figure out what to do with characters.
If Yapeal disables the keys itself, this may be a great way to notify users that it's inactive if it's decided to get rid of user-disabled keys (per the food for though of issue #8)