Re: [SyncEvolution] getting started with gSSO (was: Re: SyncEvolution + SSO + credentials)

On Wed, 2013-07-24 at 08:04 +0000, Valluri, Amarnath wrote: Got it. It's installed such that it can be auto-acticated via D-Bus. I start gsignond manually: gsignond-Message: 114849.429844 /home/pohly/src/accounts-sso/accounts-sso.gsignond/src/daemon/main.c:150 main server started at : unix:path=/tmp/testing/temp-testpim/cache/gsignond/bus-sock gsignond-Message: 114849.429922 /home/pohly/src/accounts-sso/accounts-sso.gsignond/src/daemon/main.c:152 main Entering main event loop When I run the fixed gsignond-oauth2-example, I get: Got a UI interaction request: {'FinalUrl': <'http://somehost/login.html'>, 'OpenUrl': <'https://somehost/somepath?response%5Ftype=code&state=fU7CgH3vjiBJS5zK41ZAcjFM4dc%3D&client%5Fid=megaclient&redirect%5Furi=http%3A%2F%2Fsomehost%2Flogin%2Ehtml&scope=Photos+Videos'>} Got an error: Returned state and generated state don't match Can someone explain how the UI interaction is meant to work with this example? user_action_required_callback() uses some hard-coded redirect URI. What's the real value that an app would use, for example with Google? Should the GTK UI pop up when using the example as it stands now? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.