On 24.9.2014 13:23, BINDU CHAITANYA TUMMALA wrote:
- Issue with http://localhost
The upstream gsso-example uses http://localhost:9999 as redirect uri.
And if we use as it then it is giving SSL handshake error while calling
authentication (gsso-example --get-google-token option).
It should work, but please check that possible proxy and device clock
settings are correct.
Alex or Amarnath could comment on any details in case there are
problems. We recently released a fix for this kind of issues, so please
make sure you have latest Tizen release.
- Issue with urn:ietf:wg:oauth:2.0:oob
If we use urn:ietf:wg:oauth:2.0:oob as redirect uri then after entering
username/password a web dialog appears which says "Please copy the below code
and paste it into your application.”
And the gsso-example never gets the token. If we need to use this oob redirect uri
in this case, as per google doc we need to listen to web title changes (the
authorization code will come as web title with the format like : Success
state=XXXXX&code=MY_ACCESS_TOKEN).
Modification of signonui-efl is required such that it listens to webkit title
changes and also gsignond-plugin-oauth should be changed so that it parses the
same accordingly.
We were originally catching the redirect URI in efl-webkit and it was
working beautifully. But then it was removed in Tizen 3.0 and only xwalk
was left without proper web widget, we had to switch to using localhost
redirect with built-in libsoup based web-server. It is not really a nice
solution, but only possible at the moment on Tizen 3.0 due to lack of
native web widget.
On platforms with proper web widget, things can be done properly...
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
