Hello and thanks for this great program that I use along with Baikal since yesterday. Is it possible, in addition to the Authorized Use of the respective user on integrate a global calendar for all users?
I imagine it to be so:
var globalNetworkCheckSettings={
href: 'https://myserver/calcard.php/principals/',
hrefLabel: null,
additionalResources: [],
forceReadOnly: null,
settingsAccount: true,
timeOut: 90000,
lockTimeOut: 10000,
delegation: true,
backgroundCalendars: true,
ignoreAlarms: false
},
href: 'https://myserver/caldav.php/public/default/',
userAuth:
{
userName: 'Publicman',
userPassword: 'PASSWORD'
},
timeOut: 90000,
lockTimeOut: 10000,
checkContentType: true,
settingsAccount: true,
delegation: true,
hrefLabel: null,
forceReadOnly: null,
ignoreAlarms: false,
backgroundCalendars: []
},
That would be great!
Best wishes
Tom
Hi,
you can use the additionalResources array (see comments and examples in config.js), but cannot change the username/password for that resource (the logged user must have access to it).
Cheers,
JM
On 17 Jun 2016, at 16:09, zyrixx zyrixx@gmx.net wrote:
Hello and thanks for this great program that I use along with Baikal since yesterday. Is it possible, in addition to the Authorized Use of the respective user on integrate a global calendar for all users?
I imagine it to be so:
var globalNetworkCheckSettings={ href: 'https://myserver/calcard.php/principals/ https://myserver/calcard.php/principals/', hrefLabel: null, additionalResources: [], forceReadOnly: null, settingsAccount: true, timeOut: 90000, lockTimeOut: 10000, delegation: true, backgroundCalendars: true, ignoreAlarms: false },
href: 'https://myserver/caldav.php/public/default/ https://myserver/caldav.php/public/default/', userAuth: { userName: 'Publicman', userPassword: 'PASSWORD' }, timeOut: 90000, lockTimeOut: 10000, checkContentType: true, settingsAccount: true, delegation: true, hrefLabel: null, forceReadOnly: null, ignoreAlarms: false, backgroundCalendars: [] },
That would be great!
Best wishes
Tom
Thanks for the quick reply, if I have understood correctly, then the DAV server Shared Calender must support?
Baikal makes currently not yet, so you have to wait then probably.
Cheers
Peer
Von: Ján Máté [mailto:jan.mate@inf-it.com] Gesendet: Freitag, 17. Juni 2016 20:24 An: davclients@inf-it.com Betreff: Re: [Inf-IT DAVcl] Public or global calendar
Hi,
you can use the additionalResources array (see comments and examples in config.js), but cannot change the username/password for that resource (the logged user must have access to it).
Cheers,
JM
On 17 Jun 2016, at 16:09, zyrixx zyrixx@gmx.net wrote:
Hello and thanks for this great program that I use along with Baikal since yesterday. Is it possible, in addition to the Authorized Use of the respective user on integrate a global calendar for all users?
I imagine it to be so:
var globalNetworkCheckSettings={
href: ' https://myserver/calcard.php/principals/ https://myserver/calcard.php/principals/',
hrefLabel: null,
additionalResources: [],
forceReadOnly: null,
settingsAccount: true,
timeOut: 90000,
lockTimeOut: 10000,
delegation: true,
backgroundCalendars: true,
ignoreAlarms: false
},
href: ' https://myserver/caldav.php/public/default/ https://myserver/caldav.php/public/default/',
userAuth:
{
userName: 'Publicman',
userPassword: 'PASSWORD'
},
timeOut: 90000,
lockTimeOut: 10000,
checkContentType: true,
settingsAccount: true,
delegation: true,
hrefLabel: null,
forceReadOnly: null,
ignoreAlarms: false,
backgroundCalendars: []
},
That would be great!
Best wishes
Tom
Hi,
On 18 Jun 2016, at 00:09, zyrixx zyrixx@gmx.net wrote:
Thanks for the quick reply, if I have understood correctly, then the DAV server Shared Calender must support?
I don't know whether this feature is called "shared calendar support", but your server simply needs to allow you to define who have access to a given calendar.
Baikal makes currently not yet, so you have to wait then probably.
then there is another way (requires basic auth) - the auth module. Using that module you can configure a fixed username/password which is returned to the authenticated user (in addition of settings for the user itself). It works as a predefined globalAccountSettings, but the authentication is handled server side (see the readme.txt for more information).
Cheers,
JM
Cheers
Peer
Von: Ján Máté [mailto:jan.mate@inf-it.com mailto:jan.mate@inf-it.com] Gesendet: Freitag, 17. Juni 2016 20:24 An: davclients@inf-it.com mailto:davclients@inf-it.com Betreff: Re: [Inf-IT DAVcl] Public or global calendar
Hi,
you can use the additionalResources array (see comments and examples in config.js), but cannot change the username/password for that resource (the logged user must have access to it).
Cheers,
JM
On 17 Jun 2016, at 16:09, zyrixx <zyrixx@gmx.net mailto:zyrixx@gmx.net> wrote:
Hello and thanks for this great program that I use along with Baikal since yesterday. Is it possible, in addition to the Authorized Use of the respective user on integrate a global calendar for all users?
I imagine it to be so:
var globalNetworkCheckSettings={ href: 'https://myserver/calcard.php/principals/ https://myserver/calcard.php/principals/', hrefLabel: null, additionalResources: [], forceReadOnly: null, settingsAccount: true, timeOut: 90000, lockTimeOut: 10000, delegation: true, backgroundCalendars: true, ignoreAlarms: false },
href: 'https://myserver/caldav.php/public/default/ https://myserver/caldav.php/public/default/', userAuth: { userName: 'Publicman', userPassword: 'PASSWORD' }, timeOut: 90000, lockTimeOut: 10000, checkContentType: true, settingsAccount: true, delegation: true, hrefLabel: null, forceReadOnly: null, ignoreAlarms: false, backgroundCalendars: [] },
That would be great!
Best wishes
Tom
Many thanks for the answer. However overwhelmed me even more the tutorial on this subject, because it is too technical for me as an ordinary user.
As a programmer you determined daily with authentication process and do their reaction, but I hang already at term auth_modul and also do not know how to do that in;-) Even with google I'm not smarter.
Cheers
Tom
Von: Ján Máté [mailto:jan.mate@inf-it.com] Gesendet: Dienstag, 21. Juni 2016 10:39 An: davclients@inf-it.com Betreff: Re: [Inf-IT DAVcl] Public or global calendar
Hi,
On 18 Jun 2016, at 00:09, zyrixx zyrixx@gmx.net wrote:
Thanks for the quick reply, if I have understood correctly, then the DAV server Shared Calender must support?
I don't know whether this feature is called "shared calendar support", but your server simply needs to allow you to define who have access to a given calendar.
Baikal makes currently not yet, so you have to wait then probably.
then there is another way (requires basic auth) - the auth module. Using that module you can configure a fixed username/password which is returned to the authenticated user (in addition of settings for the user itself). It works as a predefined globalAccountSettings, but the authentication is handled server side (see the readme.txt for more information).
Cheers,
JM
Cheers
Peer
Von: Ján Máté [ mailto:jan.mate@inf-it.com mailto:jan.mate@inf-it.com] Gesendet: Freitag, 17. Juni 2016 20:24 An: mailto:davclients@inf-it.com davclients@inf-it.com Betreff: Re: [Inf-IT DAVcl] Public or global calendar
Hi,
you can use the additionalResources array (see comments and examples in config.js), but cannot change the username/password for that resource (the logged user must have access to it).
Cheers,
JM
On 17 Jun 2016, at 16:09, zyrixx < mailto:zyrixx@gmx.net zyrixx@gmx.net> wrote:
Hello and thanks for this great program that I use along with Baikal since yesterday. Is it possible, in addition to the Authorized Use of the respective user on integrate a global calendar for all users?
I imagine it to be so:
var globalNetworkCheckSettings={
href: ' https://myserver/calcard.php/principals/ https://myserver/calcard.php/principals/',
hrefLabel: null,
additionalResources: [],
forceReadOnly: null,
settingsAccount: true,
timeOut: 90000,
lockTimeOut: 10000,
delegation: true,
backgroundCalendars: true,
ignoreAlarms: false
},
href: ' https://myserver/caldav.php/public/default/ https://myserver/caldav.php/public/default/',
userAuth:
{
userName: 'Publicman',
userPassword: 'PASSWORD'
},
timeOut: 90000,
lockTimeOut: 10000,
checkContentType: true,
settingsAccount: true,
delegation: true,
hrefLabel: null,
forceReadOnly: null,
ignoreAlarms: false,
backgroundCalendars: []
},
That would be great!
Best wishes
Tom