04-02-2015, 08:55 AM
Hi,
we have changed Google calendar authentication in Corebos from the one you are showing in the screenshot. That's a Service Account authentication and
you need to create a service account in google console to use it, downloading the file from the console and uploading it in Corebos in the same interface (the name is used in the filekey field).
You have to put the email address in Login , the api developers key (clé de l'API) in API key and the client id of the service account (Identifiant client) , only the part
before .apps.googleusercontent.com though.
But you have to do this for every user and that's why we have made it easier. As you can see in the screenshot, now you can use the client id
for web applications putting the client id (same as before) and the client secret , the API key (same as before) and the redirect uri which is <!-- m --><a class="postlink" href="http://yourcorebosurl/sync.php">http://yourcorebosurl/sync.php</a><!-- m -->
You have to create it only for one user (admin for example) and all the others will authorize Google Sync with their own credentials (user and password).
You have to update Corebos to the newest changes to get this modification and don't forget to load the corebosUpdater changes and apply them because
the database changes for google calendar sync to work, are in there.
Here's some documentation that you may find helpful about Google Calendar sync:
<!-- m --><a class="postlink" href="http://corebos.org/documentation/doku.php?id=en:calendar_google_integration">http://corebos.org/documentation/doku.p ... ntegration</a><!-- m -->
we have changed Google calendar authentication in Corebos from the one you are showing in the screenshot. That's a Service Account authentication and
you need to create a service account in google console to use it, downloading the file from the console and uploading it in Corebos in the same interface (the name is used in the filekey field).
You have to put the email address in Login , the api developers key (clé de l'API) in API key and the client id of the service account (Identifiant client) , only the part
before .apps.googleusercontent.com though.
But you have to do this for every user and that's why we have made it easier. As you can see in the screenshot, now you can use the client id
for web applications putting the client id (same as before) and the client secret , the API key (same as before) and the redirect uri which is <!-- m --><a class="postlink" href="http://yourcorebosurl/sync.php">http://yourcorebosurl/sync.php</a><!-- m -->
You have to create it only for one user (admin for example) and all the others will authorize Google Sync with their own credentials (user and password).
You have to update Corebos to the newest changes to get this modification and don't forget to load the corebosUpdater changes and apply them because
the database changes for google calendar sync to work, are in there.
Here's some documentation that you may find helpful about Google Calendar sync:
<!-- m --><a class="postlink" href="http://corebos.org/documentation/doku.php?id=en:calendar_google_integration">http://corebos.org/documentation/doku.p ... ntegration</a><!-- m -->