[
https://issues.apache.org/jira/browse/OPENMEETINGS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462170#comment-16462170
]
Leonid edited comment on OPENMEETINGS-1865 at 5/3/18 9:35 AM:
--------------------------------------------------------------
[~solomax] first of all thanks for your support.
Regarding Calendar:
* I updated OM to the latest:
|Name|OpenMeetings|
|Version|4.0.4-SNAPSHOT|
|Revision|87a0a5b|
|Build date|2018-04-28T13:10:22Z|
* I read the article regarding depricated link
*[https://www.google.com/calendar/dav*] and used new ones
* I re-enabled both *Google Calendar* and *Google CalDAV* APIs
* I created an OAuth credentials
* I added a redirect path for OAuth
* I created an API-key (it has only digits and letters)
* I did OAuth integration (worked fine)
I've tried to add Calendars (both as CalDAV and Google Calendar), but had no
luck:
# When adding a Calendar with "Google Calendar" checked and filling in *Google
Calendar ID* and *Google Calendar API key* I do have this calendar in my
calendars list, but it's no Syncing. And also there is no calendar to choose in
a list when creating an event. My settings were:
Title: *Calendar_Name*
Google Calendar ID:
*[https://calendar.google.com/calendar/ical/user%40domain.com(or]
gmail.com)/private-some_digits_and_letters/basic.ics*
Google Calendar *API key: My_API_key_from_Google_APIs_and_Services*
Google Calendar: *Checked*
# When adding a Calendar with ordinary CalDAV I get a message - _Error in
making connection on the URL specified._ My settings were:
Title: *Calendar_Name*
External CalDAV Calendar URL:
*[https://apidata.googleusercontent.com/caldav/v2/[email protected](or]
gmail.com)/user(or events; or blank after last "/")*
Username: *[email protected]*
Password: *some_password*
Google Calendar: *Unchecked*
Some strings from my log:
{code:java}
My Logs (sorry, the messages mixed up with Google Calendar and CalDAV):
DEBUG 05-03 12:14:07.187 o.a.o.d.u.AuthLevelUtil:42 [0.0-5080-exec-2] - Level
Admin :: [GRANTED]
DEBUG 05-03 12:14:07.359 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:09.296 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-8] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:10.392 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-1] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:17.533 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-6] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:21.279 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:22.245 o.a.o.w.u.c.CalendarPanel:86 [0.0-5080-exec-8] -
CalDAV Syncing has begun
DEBUG 05-03 12:14:22.279 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:27.584 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:33.282 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:37.624 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-6] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:45.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:47.669 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:57.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:57.741 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:07.782 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-8] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:09.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:17.833 o.a.o.d.d.c.AppointmentDao:158 [.0-5080-exec-10] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:21.269 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:27.882 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:33.275 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:37.929 o.a.o.d.d.c.AppointmentDao:158 [.0-5080-exec-10] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:45.280 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-5] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
{code}
Any ideas?
was (Author: lpervak):
[~solomax] first of all thanks for your support.
Regarding Calendar:
* I read the article regarding depricated link
*https://www.google.com/calendar/dav* and used new ones
* I re-enabled both *Google Calendar* and *Google CalDAV* APIs
* I created an OAuth credentials
* I added a redirect path for OAuth
* I created an API-key (it has only digits and letters)
* I did OAuth integration (worked fine)
I've tried to add Calendars (both as CalDAV and Google Calendar), but had no
luck:
# When adding a Calendar with "Google Calendar" checked and filling in *Google
Calendar ID* and *Google Calendar API key* I do have this calendar in my
calendars list, but it's no Syncing. And also there is no calendar to choose in
a list when creating an event. My settings were:
Title: *Calendar_Name*
Google Calendar ID:
*https://calendar.google.com/calendar/ical/user%40domain.com(or
gmail.com)/private-some_digits_and_letters/basic.ics*
Google Calendar *API key: My_API_key_from_Google_APIs_and_Services*
Google Calendar: *Checked*
# When adding a Calendar with ordinary CalDAV I get a message - _Error in
making connection on the URL specified._ My settings were:
Title: *Calendar_Name*
External CalDAV Calendar URL:
*https://apidata.googleusercontent.com/caldav/v2/[email protected](or
gmail.com)/user(or events; or blank after last "/")*
Username: *[email protected]*
Password: *some_password*
Google Calendar: *Unchecked*
Some strings from my log:
{code:java}
My Logs (sorry, the messages mixed up with Google Calendar and CalDAV):
DEBUG 05-03 12:14:07.187 o.a.o.d.u.AuthLevelUtil:42 [0.0-5080-exec-2] - Level
Admin :: [GRANTED]
DEBUG 05-03 12:14:07.359 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:09.296 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-8] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:10.392 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-1] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:17.533 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-6] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:21.279 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:22.245 o.a.o.w.u.c.CalendarPanel:86 [0.0-5080-exec-8] -
CalDAV Syncing has begun
DEBUG 05-03 12:14:22.279 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:27.584 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:33.282 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:37.624 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-6] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:45.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:47.669 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:57.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:14:57.741 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-3] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:07.782 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-8] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:09.278 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:17.833 o.a.o.d.d.c.AppointmentDao:158 [.0-5080-exec-10] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:21.269 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-4] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:27.882 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-2] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:33.275 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-7] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:37.929 o.a.o.d.d.c.AppointmentDao:158 [.0-5080-exec-10] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
DEBUG 05-03 12:15:45.280 o.a.o.d.d.c.AppointmentDao:158 [0.0-5080-exec-5] -
Start Sun Apr 29 00:00:00 EEST 2018 End Sun Jun 10 00:00:00 EEST 2018
{code}
Any ideas?
> Calendar sync fails after logout OM profile (Google calendar via CalDAV)
> ------------------------------------------------------------------------
>
> Key: OPENMEETINGS-1865
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1865
> Project: Openmeetings
> Issue Type: Improvement
> Components: HTML5/Calendar
> Affects Versions: 4.0.2, 4.0.3
> Reporter: Leonid
> Assignee: Maxim Solodovnik
> Priority: Major
>
> *Calendar sync fails after logout OpenMeetings profile.*
> _(At this point I've tried ONLY Google CalDAV - had no time to test it with
> some others)_
>
> I was able to connect to Google Calendar via CalDAV (personal and G Suit):
> *External CalDAV Calendar URL:*
> [https://www.google.com/calendar/dav/[email protected]/events]
> *Username:* [[email protected]|mailto:[email protected]]
> *Password:* MyPassword
>
> *What's working after I've added Google Calendar* (as CalDAV):
> # I'm able to sync my existing events from Google calendar to OM.
> # I can create an event for this particular Google Calendar (by selecting
> appropriate calendar when creating event).
> # I can see newly created events via Google Calendar in the OM calendar.
> # I can change/delete in both Google Calendar/OM - sync is working perfectly
> between them.
> # I can press sync button and it works - events are really synced for
> several seconds faster as OM would sync it automatically.
> *But after I log out and log in OM:*
> # I can only see events, which were created before I log out.
> # OM and Google calendar are on their own - they can't sync with each other,
> when there are creations/changes/delete of events in Google calendar and/or
> in OM.
> # When I click on Calendar name in OM I can only change the name of the
> calendar, but not credential side.
> # When clicking the Sync button a "syncing wheel" appears for a second or
> two BUT it doesn't make any sense - sync is not working.
> *I can delete Google calendar sync and create it again, but it works only
> before I log out.*
> _P.S. I couldn't set up my Google Calendar via OM's standard option for
> Google (if somebody has it working please tell me, what are the correct API
> key (I've created some in Google Dev Console, tried some tutorials but still
> no luck))._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
