You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(8) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(12) |
Mar
(8) |
Apr
|
May
(10) |
Jun
(14) |
Jul
(20) |
Aug
(11) |
Sep
(3) |
Oct
(14) |
Nov
(18) |
Dec
(5) |
2005 |
Jan
(21) |
Feb
(7) |
Mar
(6) |
Apr
(16) |
May
(9) |
Jun
(8) |
Jul
(2) |
Aug
(4) |
Sep
(15) |
Oct
(12) |
Nov
|
Dec
|
2006 |
Jan
(7) |
Feb
|
Mar
(6) |
Apr
(10) |
May
(8) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(2) |
Nov
(16) |
Dec
|
2007 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(6) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: abhi k. <abh...@gm...> - 2006-11-14 06:43:55
|
Is there some location from where i could get the documentaton, use etc? -- Love Abhi Kalyan |
From: Andreas H. <aha...@te...> - 2006-11-10 13:13:04
|
On Thu, Nov 09, 2006 at 12:26:48PM +0100, Bjorn Ove Grotan wrote: > Please test and give us feedback if you find any bugs or problems. Trying pre2. I have an "ou" with thousands of children. When I click on it *without* opening the tree (i.e., I *don't* click on the + sign) it takes a long time. I think luma is for some reason fetching all entries even though they are not going to be displayed. |
From: Andreas H. <aha...@te...> - 2006-11-10 13:01:36
|
On Thu, Nov 09, 2006 at 12:26:48PM +0100, Bjorn Ove Grotan wrote: > I've packaged a pre-build of Luma 2.4, and made it available > at http://www.grotan.com/luma/build/luma-2.4pre1.tar.bz2 > > This release will become the upcoming 2.4-release and features some bugfixes > as well as a long-awaited feature. This shiny new feature enable you to be > prompted for a password instead of storing it in the configuration-file > generated by Luma. To take advantage of this new feature, store a > valid binddn in the server-dialog, but leave password blank. > > The install-script (install.py) is also enhanced, so you can install Luma > into non-existing directories - i.e. it will create all directories needed > to create the whole tree from the --prefix argument. The CVS-version of Luma > should from now on be more easily used by our users as well as developers. Would be cool if the install.py script supported something like DESTDIR in autoconf. For example, for rpm packaging install.py used to be called with --prefix=/tmp/dir/usr, which now doesn't work because a symlink is made for the /usr/bin/luma script. The symlink ends up pointing to the temporary directory. |
From: Bjorn O. G. <bg...@gr...> - 2006-11-09 11:27:02
|
I've packaged a pre-build of Luma 2.4, and made it available at http://www.grotan.com/luma/build/luma-2.4pre1.tar.bz2 This release will become the upcoming 2.4-release and features some bugfixes as well as a long-awaited feature. This shiny new feature enable you to be prompted for a password instead of storing it in the configuration-file generated by Luma. To take advantage of this new feature, store a valid binddn in the server-dialog, but leave password blank. The install-script (install.py) is also enhanced, so you can install Luma into non-existing directories - i.e. it will create all directories needed to create the whole tree from the --prefix argument. The CVS-version of Luma should from now on be more easily used by our users as well as developers. Please test and give us feedback if you find any bugs or problems. I will wait some time before I'll package Luma for Debian/Ubuntu. The latest Debianized Luma is as always apt'able at: 'deb(-src) http://www.grotan.com/luma/ ./' -- Regards Bjørn Ove Grøtan Luma Project Admin & Debian Maintainer |
From: chris <tu...@he...> - 2006-10-18 23:45:14
|
Dave Love <fx <at> gnu.org> writes: > > If I try to expand (apparently) any account entry on an active > directory server, it fails like this: > --snip--- > tmpList.append(x.decode('utf-8')) > File "encodings/utf_8.py", line 16, in decode > Reason: exceptions.UnicodeDecodeError 'utf8' codec can't decode byte 0x80 in position 3: unexpected > code byte > > It's happy displaying, say, a computer entry from the directory. This > is with luma 2.3 plus python-ldap 2.2 on current Ubuntu. > > Sorry I don't have time to try to debug it. I may be able to provide > example LDIF, if that helps, but I'd have to worry about what's in it > as this only seems to happen for account entries. Hi have experienced this too. What I find is the following... ----------- Newly Created user accounts in Active directory can be view with LUMA. Once I have created a Mailbox in Exchange for the new user (via Exchange Tasks) the errors described below occour when viewing the account entry in LUMA. LUMA shows "Distribution Groups" I created properly with the correct email addresses from the directory. ----------- I have not explored it further. Chris |
From: Dave L. <fx...@gn...> - 2006-10-06 16:22:25
|
If I try to expand (apparently) any account entry on an active directory server, it fails like this: 17:13:29 An unhandled exception occured. This is most likely a bug in the programming of Luma. In order to fix this, send an email with the following text and a detailed description of what you were doing to lum...@li.... File "/usr/lib/luma/base/utils/gui/BrowserWidget.py", line 149, in itemClicked self.emit(PYSIGNAL("ldap_result"), (deepcopy(result),)) File "/usr/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 136, in initView self.displayValues() File "/usr/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 177, in displayValues tmpList.append(self.createAttributeString()) File "/usr/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 291, in createAttributeString valueList = self.ldapDataObject.getAttributeValueList(x) File "/usr/lib/luma/base/backend/SmartDataObject.py", line 183, in getAttributeValueList tmpList.append(x.decode('utf-8')) File "encodings/utf_8.py", line 16, in decode Reason: exceptions.UnicodeDecodeError 'utf8' codec can't decode byte 0x80 in position 3: unexpected code byte It's happy displaying, say, a computer entry from the directory. This is with luma 2.3 plus python-ldap 2.2 on current Ubuntu. Sorry I don't have time to try to debug it. I may be able to provide example LDIF, if that helps, but I'd have to worry about what's in it as this only seems to happen for account entries. |
From: Bill C. <bil...@ui...> - 2006-08-30 21:48:16
|
Hello, I'm attempting to use Luma against the local Active Directory setup and getting a weird error when attempting a search. Background: Luma 2.3 on Gentoo with latest stable supporting libs (python-ldap, cyrus sasl). Kerberos auth is working fine. ldapsearch gets the search results I'm expecting. Here's the syntax I'm using for that (munged): ldapsearch -H ldap://windowsdc \ -b dc=xxx,dc=xxx,dc=xxx \ cn=me The same search in Luma fails with: LDAP search operation failed. Reason: {'info': '00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece', 'desc': 'Operations error'} Any ideas what I should pursue here? Searches on other base DNs work, I can browse/search through those with no issue, just the base DN I actually care about it giving me this error. Thanks, -- Bill Carlson -- Systems Administrator bil...@ui... | Anything is possible, HCIS | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. | |
From: Daniel K. <d.k...@be...> - 2006-08-24 17:00:03
|
Hi list, i just configured my LDAP server to use client certificates (SASL EXTERNAL) for authentication. Works from my Laptop very will with tools like ldapsearch work perfectly. The only thing luma tells me is: 18:56:23 Certificate error. Reason: Could not set client certificate and certificate keyfile. 18:56:23 LDAP bind operation not successful. Reason: {'desc': "Can't contact LDAP server"} On the LDAP server i can only the a connect but nothing more: Aug 24 16:57:34 nagios1 slapd[10840]: conn=553 fd=22 ACCEPT from IP=xx.xx.x.xx:40810 (IP=0.0.0.0:389) Aug 24 16:57:34 nagios1 slapd[10840]: conn=553 op=1 UNBIND Aug 24 16:57:34 nagios1 slapd[10840]: conn=553 fd=22 closed Here's my ~/.ldaprc TLS_CACERT /etc/openldap/ssl/ca-bundle.crt TLS_CERT /etc/openldap/ssl/admin.cert.pem TLS_KEY /etc/openldap/ssl/admin.key.pem TLS_REQCERT demand SASL_MECH EXTERNAL So why isn't this working. I'm really running out of ideas. Regards Daniel |
From: Bjorn O. G. <bg...@sa...> - 2006-08-09 11:10:16
|
Daniel Roche: > Hello, > > i am just testing luma for the first time, > > i am trying to connect to a MS ActiveDirectory server > and browse my account > > i have defined the server, i am binding with the simple mechanism > with my DN, and the connection was successful, > i can browse the tree under the baseDN i have specified > > when i click on the leaf corresponding to my account i get the following > message : Could you supply us with an ldif-representation of that object? plain old ldapsearch should be plenty helpful with this. -- Regards Bjørn OVe Grøtan |
From: Daniel R. <d....@le...> - 2006-08-08 12:15:59
|
Hello, i am just testing luma for the first time, i am trying to connect to a MS ActiveDirectory server and browse my account i have defined the server, i am binding with the simple mechanism with my DN, and the connection was successful, i can browse the tree under the baseDN i have specified when i click on the leaf corresponding to my account i get the following message : File "/usr/local/lib/luma/base/utils/gui/BrowserWidget.py", line 149, in itemClicked self.emit(PYSIGNAL("ldap_result"), (deepcopy(result),)) File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 136, in initView self.displayValues() File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 177, in displayValues tmpList.append(self.createAttributeString()) File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 291, in createAttributeString valueList = self.ldapDataObject.getAttributeValueList(x) File "/usr/local/lib/luma/base/backend/SmartDataObject.py", line 183, in getAttributeValueList tmpList.append(x.decode('utf-8')) File "/usr/lib/python2.4/encodings/utf_8.py", line 16, in decode return codecs.utf_8_decode(input, errors, True) Reason: exceptions.UnicodeDecodeError 'utf8' codec can't decode byte 0x80 in position 3: unexpected code byte if i can do some more test to help you, feel free to ask. i precise that i can browse the same data with other tools ( JXplorer ) without problem. Best Regards -- =============================================================================== | __/ _ _ o _ / /_) _ _ / _ | mailto:d....@le... | | (_/ (_(_ / ) ( (-' / /\ (_) (_ /) (-' | http://www.lectra.com | =============================================================================== |
From: Peter M. <pe...@ad...> - 2006-07-30 15:21:01
|
Hi, While browsing an attribute definition with syntax Directory String but without an ORDERING matching rule in LUMA 2.3's Schemabrowser I came across the following error message: 17:12:42 An unhandled exception occured. This is most likely a bug in the programming of Luma. In order to fix this, send an email with the following text and a detailed description of what you were doing to lum...@li.... File "/usr/lib/luma/plugins/schemabrowser/SchemaView.py", line 218, in attributeSelected self.orderingAttributeEdit.setText(attributeDataDict['ORDERING']) Reason: exceptions.RuntimeError cannot pass None as argument 0 in this call Similar messages are displayed when attribute definitions do not have an EQUALITY matching rule, ..... This may be the cause for the issue that the list "Used in Object Classes" is empty and the check boxes "Single value", "Collective" and "Obsolete" are not filled.- BTW: It would be nice to have the Syntax field clickable and jump to the respective syntax definition on the "LDAP syntaxes" page the same way attribute names are clickable in a bloct class definition. Thanks for LUMA Peter -- Peter Marschall pe...@ad... |
From: Andreas H. <aha...@te...> - 2006-05-31 21:18:58
|
The subject line is probably not clear enough. The problem is that luma sees "userid" and "uid" as different attributes when they are actually the same: attributetype ( 0.9.2342.19200300.100.1.1 NAME ( 'uid' 'userid' ) EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} ) I have a template with two object classes: account and posixAccount. "account" requires (MUST) "userid": objectclass ( 0.9.2342.19200300.100.4.5 NAME 'account' SUP top STRUCTURAL MUST userid MAY ( description $ seeAlso $ localityName $ organizationName $ organizationalUnitName $ host ) ) "posixAccount" requires (MUST) "uid": objectclass ( 1.3.6.1.1.1.2.0 NAME 'posixAccount' DESC 'Abstraction of an account with POSIX attributes' SUP top AUXILIARY MUST ( cn $ uid $ uidNumber $ gidNumber $ homeDirectory ) MAY ( userPassword $ loginShell $ gecos $ description ) ) So luma is requiring both userid and uid, but these attributes are the same. This leads to an error when inserting such an entry. |
From: Wido D. <wid...@gm...> - 2006-05-21 16:28:06
|
On 4/12/06, Andreas Hasenack <aha...@te...> wrote: > luma-2.3 > > On the massive user creation plugin, click on the folder icon in > Directory Location/Base node, select the node and hit Ok. This backtrace > shows up: > > File "/usr/lib/luma/base/utils/gui/BrowserDialog.py", line 110, in > checkInput > tmpText = self.tmpBrowser.getFullPath(tmpItem) > Reason: exceptions.AttributeError getFullPath > > I selected the ou=Prople branch. Confirmed and fixed. Bugfixrelease will be out this week. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Wido D. <wid...@gm...> - 2006-05-21 14:38:47
|
On 5/3/06, Andreas Hasenack <aha...@te...> wrote: > I have a faulty ALT key and, sometimes when I switch desktops using > ALT-<number> something else gets sent. When luma is focused, the browser > tree to the left suddenly turns into grey (like read-only) and the bomb > icon lights up with this: > > File "/usr/lib/luma/base/utils/gui/BrowserWidget.py", line 876, in > keyPressEvent > if keyTex == tmpString[0].lower(): > Reason: exceptions.NameError global name 'keyTex' is not defined The browser turns grey because it has keyboard focus and starts seaching the next element with the typed key at the beginning of the dn. The error you got should be fixed now. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Wido D. <wid...@gm...> - 2006-05-21 14:05:24
|
On 5/11/06, Vincent Cruz <cru...@gm...> wrote: > Hello, > > I'm runing Luma 2.3 with python-ldap 2.0.6, PyQt 3.15 and Qt 3.3.5. > I'm trying to set the "usercertificate;binary" attribute for an entry. > So i'm clicking on the "Edit attribute" icon, but i have the following > error when i click on the file browser icon: > > File "/usr/local/lib/luma/base/utils/gui/editors/BinaryEditor.py", > line 70, in showFileDialog > None, 1) > Reason: exceptions.RuntimeError cannot pass None as argument 0 in this call > > But i'm still able to add a certificate (provided it's encoded in > DER format). Then i'm trying to save the "usercertificate;binary" from > another user. When i click on the save/export icon, i have the > following error: > > File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", > line 446, in modifierClicked > self.exportAttribute(attributeName, index) > File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", > line 461, in exportAttribute > None, 1)) > Reason: exceptions.RuntimeError cannot pass None as argument 0 in this call > > Ps: I attached the ldif and the certificate in DER format, i used for tests. > > Regards, > Vincent > > > Confirmed and fixed. Bugfixrelease will be out this week. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Wido D. <wid...@gm...> - 2006-05-21 13:29:31
|
On 4/26/06, Andreas Hasenack <aha...@te...> wrote: > OpenLDAP supports an EXOP for password changes. This means the hash > is not done by the client, but by the server with whatever scheme the > server is configured to use. > > This could be added to the password change dialog as another option > (called "exop" or "use extended operation", for example) among the > schemes that are already there. Sounds good to me. I'll have a look at current python-ldap and see how this can be done. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Vincent C. <cru...@gm...> - 2006-05-11 12:53:20
|
Hello, I'm runing Luma 2.3 with python-ldap 2.0.6, PyQt 3.15 and Qt 3.3.5. I'm trying to set the "usercertificate;binary" attribute for an entry. So i'm clicking on the "Edit attribute" icon, but i have the following error when i click on the file browser icon: File "/usr/local/lib/luma/base/utils/gui/editors/BinaryEditor.py", line 70, in showFileDialog None, 1) Reason: exceptions.RuntimeError cannot pass None as argument 0 in this call But i'm still able to add a certificate (provided it's encoded in DER format). Then i'm trying to save the "usercertificate;binary" from another user. When i click on the save/export icon, i have the following error: File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 446, in modifierClicked self.exportAttribute(attributeName, index) File "/usr/local/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 461, in exportAttribute None, 1)) Reason: exceptions.RuntimeError cannot pass None as argument 0 in this call Ps: I attached the ldif and the certificate in DER format, i used for tests= . Regards, Vincent |
From: Andreas H. <aha...@te...> - 2006-05-10 20:11:13
|
luma-2.3 I have an address book entry based on the inetOrgPerson objectClass. It has two street attributes. When I try to remove the one which has an accented character, I get this backtrace: File "/usr/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 444, in modifierClicked self.deleteAttribute(attributeName, index) File "/usr/lib/luma/base/utils/gui/AdvancedObjectWidget.py", line 506, in deleteAttribute self.ldapDataObject.deleteAttributeValue(attributeName, index) File "/usr/lib/luma/base/backend/SmartDataObject.py", line 614, in deleteAttributeValue if self.isAttributeValueRDN(attributeName, self.data[attributeName][index]): File "/usr/lib/luma/base/backend/SmartDataObject.py", line 515, in isAttributeValueRDN tmpRDN = attributeName + "=" + attributeValue Reason: exceptions.UnicodeDecodeError 'ascii' codec can't decode byte 0xc3 in position 4: ordinal not in range(128) |
From: Andreas H. <aha...@te...> - 2006-05-03 13:37:18
|
I have a faulty ALT key and, sometimes when I switch desktops using ALT-<number> something else gets sent. When luma is focused, the browser tree to the left suddenly turns into grey (like read-only) and the bomb icon lights up with this: File "/usr/lib/luma/base/utils/gui/BrowserWidget.py", line 876, in keyPressEvent if keyTex == tmpString[0].lower(): Reason: exceptions.NameError global name 'keyTex' is not defined |
From: Andreas H. <aha...@te...> - 2006-04-26 14:56:02
|
OpenLDAP supports an EXOP for password changes. This means the hash is not done by the client, but by the server with whatever scheme the server is configured to use. This could be added to the password change dialog as another option (called "exop" or "use extended operation", for example) among the schemes that are already there. One benefit of this is for when one uses openldap's new password policy overlay, which intercepts password changes and applies policies to them. If supplying the password already as a hash, the policy can't be applied because the clear text password is unknown. But if using exop, the password is provided in clear text and the server can then test it for the security policies that were configured. And, if the new password passes the tests, it gets hashed by the server and stored. The other benefit is that there is no risk of ever using a hash algorithm or implementation that the server happens to not support. There are some workarounds one can use while exop is not implemented in luma: select "clear text" in luma and enable ppolicy_hash_cleartext on the server. It's description says (emphasis mine): ppolicy_hash_cleartext Specify that cleartext passwords present in Add and Modify requests should be hashed before being stored in the database. This violates the X.500/LDAP information model, but may be needed to compensate for LDAP clients that don't use the Pass- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ word Modify extended operation to manage passwords. It is rec- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ommended that when this option is used that compare, search, and read access be denied to all directory users. |
From: Andreas H. <aha...@te...> - 2006-04-12 20:46:31
|
luma-2.3 On the massive user creation plugin, click on the folder icon in Directory Location/Base node, select the node and hit Ok. This backtrace shows up: File "/usr/lib/luma/base/utils/gui/BrowserDialog.py", line 110, in checkInput tmpText = self.tmpBrowser.getFullPath(tmpItem) Reason: exceptions.AttributeError getFullPath I selected the ou=Prople branch. |
From: Andreas H. <aha...@te...> - 2006-04-04 17:46:24
|
On Tue, Apr 04, 2006 at 07:09:28PM +0200, Wido Depping wrote: > On 3/31/06, Andreas Hasenack <aha...@te...> wrote: > > (luma-2.3) > > > > 1) singlevalue info about an attribute is not shown. Test with the > > gecos attribute, which is SINGLE-VALUE > > > > 2) when viewing attributes, the "used in objectclasses" window-pane is > > always empty > > Both of your observations result from the same error. Some schema > values were not properly handled and resulted in a runtime exception. > You should have gotten an bomb symbol in the lower right corner, which > described the error. I've fixed this and everything seems to be normal Ah, the bomb icon, ok, now I see it (and it was there all the time). I will be sure to check it out if I encounter something weird again :) |
From: Wido D. <wid...@gm...> - 2006-04-04 17:23:56
|
On 3/21/06, Andreas Hasenack <aha...@te...> wrote: > Is there a way to add an aux objectClass to an already existing entry wit= h > luma-2.3? This works by adding an attribute which is supplied by the aux objectclass. Unfortunately this isn't possible now without adding an attribute. Again, Luma3 will fix this. I want to use the limited time I have, in order to do the architecture and handling of the next version right, instead of fixing 'broken' stuff. Hopefully you'll understand this. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Wido D. <wid...@gm...> - 2006-04-04 17:09:33
|
On 3/31/06, Andreas Hasenack <aha...@te...> wrote: > (luma-2.3) > > 1) singlevalue info about an attribute is not shown. Test with the > gecos attribute, which is SINGLE-VALUE > > 2) when viewing attributes, the "used in objectclasses" window-pane is > always empty Both of your observations result from the same error. Some schema values were not properly handled and resulted in a runtime exception. You should have gotten an bomb symbol in the lower right corner, which described the error. I've fixed this and everything seems to be normal again. 2.3.1 will contain the fix. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |
From: Wido D. <wid...@gm...> - 2006-04-04 16:27:02
|
On 4/4/06, Andreas Hasenack <aha...@te...> wrote: > (luma-2.3) > > I experienced this twice with different servers, so I thought I should > report it. > > When using luma to access a w2k AD, the schema entry is not available to > luma, probably because it's in a different place than openldap or just > because of ACLs. This makes luma not show any entry, always failing with > errors of the type: > > Could not display ldap entry. Reason: > ObjectClass <someclass> not present in server schema. > > > Now I got the same error while browsing openldap's cn=3Dmonitor tree > (enabled via the back_monitor.la backend): > > Could not display ldap entry. Reason: > ObjectClass monitorContainer not present in server schema. > > > Not sure if it's an openldap. I don't know if it should > publish the schema for these internal entries. Hi Andreas, The current design of Luma requires the schemas to be accessible for the user, in order to do sane error preventing. Back when I made this descision, the world was okay. No Active Directory and no monitor backend were on the horizon. So I made schema info a requirement. Unfortunately this bites my ass now :-/ With some quick hacks I could make this working, but I'm sure it will introduce some errors. So there is no real short term solution. Luckily I'm redesigning the Luma libraries and architecture for the Qt4 port. One of the new features will be, that basic operations will work without a schema. This should fix your problems and additionally make Luma a better LDAP platform. I can't give you a date when this stuff will be released, since this requires PyQt4 to leave beta status, but 1-3 months sounds possible. mfg. Wido -- Wido Depping ICQ: 51303067 AIM: wido3379 Jabber: wi...@ja... |