October 2009 - calendarserver-dev - lists.macosforge.org

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 14 Oct '09

14 Oct '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: sagen@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): I would like to know whether anyone is using this patch in a production environment. I am using this patch with calendarserver in a company with about 250 users simultaneously connected with Lightning. The error log shows that authentication has failed for about 4-5 users and it keeps on retrying continuously. The calendar server process initially starts normally but suddenly its cpu usage goes to above 90%. The server is a Intel Core 2 1.86 Ghz CPU with more than 3 GB RAM. I am trying to figure out the possible reason for the high CPU usage. 1. The server configuration is not sufficient for 250 simultaneous users. 2. The ldap patch is coded in a way which is leading to the high CPU usage. 3. The repeated authentication attempts is leading to the high CPU usage. Any help in this regard would be highly appreciated. -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:34> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 07 Oct '09

07 Oct '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: sagen@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): The patch should work exactly this way. I have just tested it. The dn and password entries should be present in the configuration file but their values should be empty. As per the code, if the user is not found in the ldap database, authentication does not proceed. Replying to [comment:31 rlalkaka@…]: > Replying to [comment:29 rahul@…]: > > I have modified the patch given to me by Oxullo to include LDAP TLS support as well as filters. Also authentication is done using PAM rather than LDAP. I have only commented out the LDAP authentication code just in case you intend to revert to using LDAP server for authentication. The configuration options are as below now (I have included a sample filter option as well). Also the tlsCACertDir option does not seem to be working (no idea as to why this option is not working). > > I'm having some trouble getting this working. Leaving the credentials field blank (which the comments in twistedcaldav/directory/ldapdirectory.py imply will anonymously bind) prompts ./run to spew errors about the blank credentials DN (log and trace below). Is there an easy way to change the patched LDAP to bind to uid=<username>,ou=people,dc=example,dc=com and then proceed with PAM auth if the record exists, instead of searching as in the current implementation? Apologies if this is a trivial change -- I can't make head or tail of LDAP right now. > > {{{ > [startup] Configuring directory service of type: twistedcaldav.directory.ldapdirectory.LdapDirectoryService > [LdapDirectoryService] Calling ldap.initialize('ldap://ldap.server- removed.com:389/'). > [-] Traceback (most recent call last): > [-] File "../Twisted/bin/twistd", line 21, in ? > [-] run() > [-] File "/tmp/src/Twisted/twisted/scripts/twistd.py", line 27, in run > [-] app.run(runApp, ServerOptions) > [-] File "/tmp/src/Twisted/twisted/application/app.py", line 379, in run > [-] runApp(config) > [-] File "/tmp/src/Twisted/twisted/scripts/twistd.py", line 23, in runApp > [-] _SomeApplicationRunner(config).run() > [-] File "/tmp/src/Twisted/twisted/application/app.py", line 157, in run > [-] self.application = self.createOrGetApplication() > [-] File "/tmp/src/Twisted/twisted/application/app.py", line 202, in createOrGetApplication > [-] ser = plg.makeService(self.config.subOptions) > [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/tap.py", line 749, in makeService > [-] service = serviceMethod(options) > [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/tap.py", line 471, in makeService_Slave > [-] baseDirectory = directoryClass(**config.DirectoryService["params"]) > [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/directory/ldapdirectory.py", line 144, in __init__ > [-] self._updateStorage(recordType) > [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/directory/ldapdirectory.py", line 238, in _updateStorage > [-] logging.info("Retrieving subtree of %s." % ldap.dn.dn2str(base), system="LdapDirectoryService") > [-] AttributeError: 'module' object has no attribute 'dn' > }}} > -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:33> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

[CalendarServer] #349: location in snow leopard...
by CalendarServer 01 Oct '09

01 Oct '09

#349: location in snow leopard... -----------------------------------+---------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Later Component: Calendar Server | Severity: Serious Keywords: location snow leopard | -----------------------------------+---------------------------------------- when using "location" text field in iCal, it accepts directly, ...even if the user is not in the proxy list in the xml file. here is the part of the xlm, where user demo can mofidy calendar (it shouldn't) : <location> <uid>rfi</uid> <guid>F2F2B56A-7B0E-498C-816F-1DA30D8A4168</guid> <password>dddd</password> <name>rfi</name> <email-address>rfi(a)location.fr</email-address> <auto-schedule/> <proxies> <member type="users">jduffas</member> </proxies> </location> -- Ticket URL: <http://trac.calendarserver.org/ticket/349> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2