Web forum is in read-only mode. Login as active registered customer for write access
  Forum Search   New Posts New Posts

CloudPack usage

 Post Reply Post Reply
Author
Didier Largange View Drop Down
New Member
New Member
Avatar

Joined: 04 May 2019
Posts: 8
Post Options Post Options   Quote Didier Largange Quote  Post ReplyReply Direct Link To This Post Topic: CloudPack usage
    Posted: 22 May 2019 at 4:54pm
Hi,
I'm investigating about using CloudPack to add Google Calendar sync capabilities to a multi user application.
I want each user to have it's events synchronized with his personal GCalendar.
I already read about retrieving API key and secret.
But:
Do I store them in the user account in the app database?
Does it require the user to have an opened Google session to synchronize?
Or can I test that the session is opened, to process silently?

Thanks for your directions.
Back to Top
Bart Holvoet View Drop Down
TMS Support
TMS Support
Avatar

Joined: 18 May 2010
Posts: 2049
Post Options Post Options   Quote Bart Holvoet Quote  Post ReplyReply Direct Link To This Post Posted: 22 May 2019 at 5:02pm
Hi,

A one time authentication and authorization process based on the API key and secret with user interaction is required.
Once a valid access token is available, no user interaction is required as long as the token remains valid. While the access token is valid there is no open Google session required.
Back to Top
Didier Largange View Drop Down
New Member
New Member
Avatar

Joined: 04 May 2019
Posts: 8
Post Options Post Options   Quote Didier Largange Quote  Post ReplyReply Direct Link To This Post Posted: 22 May 2019 at 5:09pm
Good news, thank you.
What do I have to store (only the token?) and where (DB, registry)?
This is a Windows client application.
Back to Top
Bart Holvoet View Drop Down
TMS Support
TMS Support
Avatar

Joined: 18 May 2010
Posts: 2049
Post Options Post Options   Quote Bart Holvoet Quote  Post ReplyReply Direct Link To This Post Posted: 23 May 2019 at 1:51pm
You can use the SaveTokens call to store an encrypted version of the current access & refresh token in the registry, a DB or an INI file.
Further details can be found in the PDF manual under the Authentication persistence topic.
This technique is also demonstrated in the demo applications.
Back to Top
Didier Largange View Drop Down
New Member
New Member
Avatar

Joined: 04 May 2019
Posts: 8
Post Options Post Options   Quote Didier Largange Quote  Post ReplyReply Direct Link To This Post Posted: 23 May 2019 at 2:11pm
Thank you!
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down