| # |
May 30th 2016, 07:30 |
voycey |
one SDK might handle multiple apps above it |
| # |
May 30th 2016, 07:30 |
voycey |
not possible really - the logins are handled through an SDK |
| # |
May 30th 2016, 07:30 |
 bravo-kernel |
banking apps do exactly the same |
| # |
May 30th 2016, 07:30 |
bravo-kernel |
just ask for password again? |
| # |
May 30th 2016, 07:29 |
voycey |
yeah me too - so I guess id have to store some other kind of token to handle the re-request |
| # |
May 30th 2016, 07:29 |
bravo-kernel |
but that's personal |
| # |
May 30th 2016, 07:29 |
bravo-kernel |
and auto-refreshing would mean storing username/password locally which is horrid if you ask me |
| # |
May 30th 2016, 07:29 |
bravo-kernel |
not authenticated anymore means re-authenticating to me |
| # |
May 30th 2016, 07:28 |
bravo-kernel |
nope |
| # |
May 30th 2016, 07:28 |
voycey |
or is there some other mechanism thats recommended to do it? |
| # |
May 30th 2016, 07:28 |
voycey |
yeah so can that expired token be used to request a new one? |
| # |
May 30th 2016, 07:27 |
bravo-kernel |
that's the whole point |
| # |
May 30th 2016, 07:27 |
bravo-kernel |
the app should only store the (user-specific) token, not the password |
| # |
May 30th 2016, 07:27 |
voycey |
logging in again isnt really an option so just wondering how other people build this |
| # |
May 30th 2016, 07:26 |
bravo-kernel |
s/one/a girl/ |
| # |
May 30th 2016, 07:26 |
voycey |
say if it was an app that was issued with a token - would the app have to store the username and password in that case? |
| # |
May 30th 2016, 07:26 |
bravo-kernel |
one may request as often as one likes |
| # |
May 30th 2016, 07:26 |
bravo-kernel |
just request a new token |
| # |
May 30th 2016, 07:25 |
voycey |
Refreshing *with a new token |
| # |
May 30th 2016, 07:25 |
voycey |
not revocation really but more like refreshing a new token |
| # |
May 30th 2016, 07:25 |
bravo-kernel |
replacements sounds like revocation and jwt was/is not meant for that |
| # |
May 30th 2016, 07:24 |
voycey |
ok I thought so - but I had a quick read around and there were all sorts of options about using another token to get a replacement |
| # |
May 30th 2016, 07:24 |
bravo-kernel |
then get a new token by using `/token` action |
| # |
May 30th 2016, 07:24 |
bravo-kernel |
jwt just throws an expired exception |
| # |
May 30th 2016, 07:23 |
bravo-kernel |
and for a reason |
| # |
May 30th 2016, 07:23 |
bravo-kernel |
no |
| # |
May 30th 2016, 07:23 |
voycey |
do you have anything on your amazing JWT tutorials about handling expired tokens? |
| # |
May 30th 2016, 07:23 |
voycey |
bravo-kernel |
| # |
May 30th 2016, 07:22 |
bravo-kernel |
pretty good result for the 1st release, I hope feedback will result in updates |
| # |
May 30th 2016, 07:21 |
bravo-kernel |
@savant: nice work on the new look n feel |
| # |
May 30th 2016, 07:18 |
Liquidedust |
remind me to take a day off after next cakeFest, was quite rough to go to work this morning |
| # |
May 30th 2016, 07:17 |
unorthodox |
Morning @Liquidedust |
| # |
May 30th 2016, 07:15 |
Liquidedust |
ACTION yawns |
| # |
May 30th 2016, 07:09 |
storkovo |
sooner. Thats cool, good to have you here. |
| # |
May 30th 2016, 07:08 |
voycey |
2006 ish? 2007 maybe? |
| # |
May 30th 2016, 07:08 |
voycey |
but I was definitely using 0.9 |
| # |
May 30th 2016, 07:08 |
voycey |
not sure when it came out of beta |
| # |
May 30th 2016, 07:08 |
voycey |
well first official one |
| # |
May 30th 2016, 07:08 |
voycey |
it probably was |
| # |
May 30th 2016, 07:08 |
storkovo |
voycey: wow, the old high and mighty man who wears my shoes used to think that 1.0 was the first public release |
| # |
May 30th 2016, 07:03 |
JohnWayne |
Its working, thx |