Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Dran Arcana
Dreddit Test Alliance Please Ignore
0
|
Posted - 2015.06.10 18:17:36 -
[1] - Quote
Is there a way to do authed crest via a console app? Or more accurately, is there a way to reliably get a token outside of a browser?
I am looking to build a on-demand database of a single station's active market orders (not jita, and at most once/day) so that users don't have to wait 40 minutes after logging in to actually use my site, and so the data can be cached and not refreshed unnecessarily. The data/requests/load saved would be exponential if I could figure out a way to do this.
And before anyone suggests it, eve-marketdata is broken and essentially un-maintained, and eve-central doesn't provide enough metadata via their API for what I'm trying to do. |
Kali Izia
GoomWaffe Goonswarm Federation
53
|
Posted - 2015.06.10 18:56:03 -
[2] - Quote
The actual user authentication has to happen from a browser. Doing anything else is wrong and defeats the purpose of Oauth.
If this is server-side code for your own use, what you should do is follow the normal flow from a browser once. You'll get a refresh token and you can hardcode that into your app.
If this is being distributed and you want other people to use their own tokens, just have the user follow the browser flow once instead. You can either get fancy and register a URI handler so your app could handle a redirect to something like yourapp://callback, or just have the user copy/paste the refresh token in and then have the app store it. |
KillaGouge
DelTacos 212
0
|
Posted - 2015.06.15 15:48:18 -
[3] - Quote
If you take a look at Evelib, they released a console app that will walk you through getting your token and refresh key.
https://github.com/ezet/evelib
As far as I understand, the refresh key is good indefinitely.
You still have to go through a browser |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
5351
|
Posted - 2015.06.16 11:55:42 -
[4] - Quote
Kali Izia wrote:The actual user authentication has to happen from a browser. Doing anything else is wrong and defeats the purpose of Oauth.
If this is server-side code for your own use, what you should do is follow the normal flow from a browser once. You'll get a refresh token and you can hardcode that into your app.
If this is being distributed and you want other people to use their own tokens, just have the user follow the browser flow once instead. You can either get fancy and register a URI handler so your app could handle a redirect to something like yourapp://callback, or just have the user copy/paste the refresh token in and then have the app store it.
The other 'fancy' way of handling it is to embed a webserver into the process, and have it callback to http://localhost:52343/ or similar.
Which is somewhat simpler than a uri handler, much of the time. (I spent some time on it. it's a pita in windows)
Woo! CSM X!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |