it should be possible you know 🙂 open the javafx browser and have the most simple of http listeners listening to the result

hmmz I feel a poc coming up

@ron I think it's a little more than faking your own HTTP and reading some HTML to avoid the browser. There's a decision that the user will be making to accept or decline. The URL takes you to a screen that says -- after you login -- "Ok to give Carl's App access to your Dropbox account?".

no no I am explaingin it wrong

you open the grant url in the webview, so the user has to answer the question to allow or not.

the callback url from oauth is what you want to catch, then you get a verification code, that you have to exchange for a access token

i think that would work. i opted for the external browser because the user might already be logged into Dropbox

damn simpleStringProperty is not serializable?

@carlw @ron I was actually thinking about using the javafx webview and listen at the redirect like http://stackoverflow.com/questions/12280391/retrieving-access-token-of-oauth-2-0-implicit-grant-from-java-desktop-client-u

@nimakro I'm not sure about your target. For me, Dropbox involved not only a credential but also an Authenticator code. I recommend the external browser. I think the WebView is ok only if you're planning on letting the user interact with it as-is and not get involved trying to parse the HTML.

I basically want to be able do authorization from within my app and then use the token for all the rest calls.

@nimakro yep. once you get the token, that is used for all the calls

Like Basic Authentication, you'll use an Authorization HTTP request header to pass along the token with each request (an API may do this for you too). That's maybe where @edvin can help with the framework

GET /resource HTTP/1.1 Host: server.example.com Authorization: Bearer mF_9.B5f-4.1JqM

@carlw I decided to go with the external browser, for the same reasons you mentioned before, but with the addition that I start a little web server , and configured the redirect_url to localhost. This way the user dons't have to manually copy the token back to the tornadofx app. As soon as the user grants access a thank you page will be shown at localhost I will parse the query params to get the code, swap the cod for a token and I am good to go...

@carlw Ah, that makes sense 🙂

@nimakro That was a neat trick.

Latest commit: Android SDK compatibilty (See https://github.com/edvin/tornadofx-android-compat)

@nimakro sounds like a good idea. my dropbox integration job was delivered years ago, but i'd like to hear any lessons you might learn working with the redirect url and getting the URL parameters back into javafx

@carlw I got It working and will post some code as soon as it I cleaned it up... I have to go now family time 😀 talk to you guys later

Bye @nimakro 🙂

@edvin maybe you could add an api.setBearerAuth("accesstoken") to tornadofx? This would translate to an addHeader("Authorization", "Bearer accesstoken") with each request

hmmz I think I would just use the api.addHeader method

I don't think that adds much value if that's the only OAuth support we add.

@edvin - I take it you renamed Fieldset.orientation to Fieldset.labelPosition between the two projects?

@gtnarg Ah, yes - I just felt orientation was too vague. We might change the backing field and deprecate the getters setters perhaps?

@edvin that kind that does sound like what I need I will play with it and follow up later

@thomasnield Good. I use it with great success for a number of projects, I have a dynamic dns client with hundreds of deployed clients. Never had any issues, and updates are super easy.

@edvin how would you set an http header for each call on an API? Does it have to be issued with each method?

I just pushed some code to kphoto. its a play project but it can now save and load json files as tags and uses the datadriven treeview