Right now, if I open up a previously saved chrome session with several pages
open on JIRA issues which require I log in, they all redirect to the login
screen where I can choose one, log in and then go hit refresh on all of the
other pages to see the actual tickets.
Does your extension do anything to alleviate this issue by perhaps blocking the
loads of JIRA ticket pages until authorization has been performed?
On the topic of authorization, is the username/password given to the extension
for one's JIRA account(s) encrypted when/if stored? Or can one choose to only
give the extension one's credentials at chrome startup time and not save them
to disk (i.e. the extension doesn't save them to disk)?
Original issue reported on code.google.com by brianjmu...@gmail.com on 12 Mar 2012 at 11:56
Original issue reported on code.google.com by
brianjmu...@gmail.com
on 12 Mar 2012 at 11:56