The primary scenario needing attention is, if the user currently has a key configured, and this configured key is nearing expiration. If there is already a selected key, and if there are additional keys that are expiring (or have already expired), the user most likely doesn't care about those additional keys (because the user is using a different key). If you want to ensure attention for the most important scenario, I'd always list the currently selected key as the topmost entry. If you want to avoid that the user gets unnecessarily confused by extra keys (which the user might have accidentally created and not yet deleted), I'd limit the amount of expired keys that are shown (e.g. to 3) as I've previously suggested. Regarding expiring keys or not expiring keys, it's difficult to say which key is more important. Another attribute might be more relevant for this decision. Most likely, the most recently created key has the highest likelihood to be user's desired choice as their selected key. If you'd like to based the order on that criteria, then sort by the keyCreated attribute (highest value is most recently created, sort descending).
Bug 1647355 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The primary scenario needing attention is, if the user currently has a key configured, and this configured key is nearing expiration (or has already expired). If there is already a selected key, and if there are additional keys that are expiring (or have already expired), the user most likely doesn't care about those additional keys (because the user is using a different key). If you want to ensure attention for the most important scenario, I'd always list the currently selected key as the topmost entry. If you want to avoid that the user gets unnecessarily confused by extra keys (which the user might have accidentally created and not yet deleted), I'd limit the amount of expired keys that are shown (e.g. to 3) as I've previously suggested. Regarding expiring keys or not expiring keys, it's difficult to say which key is more important. Another attribute might be more relevant for this decision. Most likely, the most recently created key has the highest likelihood to be user's desired choice as their selected key. If you'd like to based the order on that criteria, then sort by the keyCreated attribute (highest value is most recently created, sort descending).
The primary scenario needing attention is, if the user currently has a key configured, and this configured key is nearing expiration (or has already expired). If there is already a selected key, and if there are additional keys that are expiring (or have already expired), the user most likely doesn't care about those additional keys (because the user is using a different key). If you want to ensure attention for the most important scenario, I'd always list the currently selected key as the topmost entry. If you want to avoid that the user gets unnecessarily confused by extra keys (which the user might have accidentally created and not yet deleted), I'd limit the amount of expired keys that are shown (e.g. to 3) as I've previously suggested. Regarding expiring keys or not expiring keys, it's difficult to say which key is more important. Another attribute might be more relevant for this decision. Most likely, the most recently created key has the highest likelihood to be user's desired choice as their selected key. If you'd like to base the order on that criteria, then sort by the keyCreated attribute (highest value is most recently created, sort descending).