[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [ldap] Re: finally, my openldap is running with mysql



what tables? the ldap_oc_mappings and the ldap_attr_maping? i have all that tables in mysql.

*********** REPLY SEPARATOR  ***********

On 1/22/2004 at 8:31 AM Michael Oberdorf wrote:

>Hello Manuel,
>
>does the Table in the SQL Backend exists?
>
>
>Regards
>Michael
>
>
>
>> yes i think it will work, but now i need to know whats happening with 
>> 
>> ldapadd -c -x -D "cn=manager,dc=sql,dc=RU" -W -f test.ldif
>> 
>> i replace the dn:manager,dc=sql,dc=RU for dc=manager,dc=sql.......
>> 
>> but it doesnt run
>> 
>> this is the new error
>> 
>>  ldapadd -c -x -D cn=manager,dc=sql,dc=RU -W -f test.ldif 
>> Enter LDAP Password: 
>> adding new entry "dc=sql,dc=RU"
>> ldapadd: update failed: dc=sql,dc=RU
>> ldap_add: Server is unwilling to perform (53)
>>         additional info: operation not permitted within namingContext
>> 
>> adding new entry "cn=manager,dc=sql,dc=RU"
>> ldapadd: update failed: cn=manager,dc=sql,dc=RU
>> ldap_add: Server is unwilling to perform (53)
>>         additional info: operation not permitted within namingContext
>> 
>> 
>> 
>> 
>> *********** REPLY SEPARATOR  ***********
>> 
>> On 1/20/2004 at 3:04 PM Otto Kucera wrote:
>> 
>> >hi manuel!
>> >
>> >do you think it will ever run? i lost my hope ... :(
>> >
>> >otto
>> >p.s.: are you from cuba?
>> >
>> >Manuel Mely wrote:
>> >
>> >> Well, after a lot of days and weeks finally my openldap server is 
>> >> running with mysql, but i can't add an ldif file i get this error.
>> >>  
>> >> l
>> >> dapadd -c -x -D "cn=manager,dc=sql,dc=RU" -W -f test.ldif
>> >> Enter LDAP Password:
>> >> adding new entry "dc=sql,dc=RU"
>> >> ldapadd: update failed: dc=sql,dc=RU
>> >> ldap_add: Server is unwilling to perform (53)
>> >>         additional info: operation not permitted within namingContext
>> >>  
>> >> adding new entry "cn:manager,dc=sql,dc=RU"
>> >> ldapadd: update failed: cn:manager,dc=sql,dc=RU
>> >> ldap_add: Invalid DN syntax (34)
>> >>         additional info: invalid DN
>> >>  
>> >> my slapd.conf
>> >>  
>> >> # access to dn.base="cn=Subschema" by * read
>> >> # access to *
>> >> #       by self write
>> >> #       by users read
>> >> #       by anonymous auth
>> >> #
>> >> # if no access controls are present, the default policy
>> >> # allows anyone and everyone to read anything but restricts
>> >> # updates to rootdn.  (e.g., "access to * by * read")
>> >> #
>> >> # rootdn can always read and write EVERYTHING!
>> >>  
>> >>
>#######################################################################
>> >> # ldbm database definitions
>> >>
>#######################################################################
>> >>  
>> >> #database       ldbm
>> >> #suffix         "dc=my-domain,dc=com"
>> >> #rootdn         "cn=Manager,dc=my-domain,dc=com"
>> >> # Cleartext passwords, especially for the rootdn, should
>> >> # be avoid.  See slappasswd(8) and slapd.conf(5) for details.
>> >> # Use of strong authentication encouraged.
>> >> #rootpw         secret
>> >> # The database directory MUST exist prior to running slapd AND
>> >> # should only be accessible by the slapd and slap tools.
>> >> # Mode 700 recommended.
>> >> #directory      /usr/local/var/openldap-data
>> >> # Indices to maintain
>> >> #index  objectClass     eq
>> >>  
>> >>
>>
>>##########################################################################
>> >> # BD test en MySQL
>> >>
>>
>>##########################################################################
>> >>  
>> >> database        sql
>> >> # This following is for the sample database as it installs
>> >> suffix          "dc=sql,dc=RU"
>> >> rootdn          "cn=manager,dc=sql,dc=RU"
>> >> rootpw          secret
>> >> dbname          test
>> >> dbuser          mely
>> >> dbpasswd        mely
>> >> at_query "SELECT 
>> >>
>>
>>name,sel_expr,from_tbls,join_where,add_proc,delete_proc,param_order,expect_
>> return 
>> >> FROM ldap_attr_mappings WHERE oc_map_id=?" insentry_query  "insert 
>> >> into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select 
>> >> max(id)+1 from ldap_entries),?,?,?,?)" upper_func      "upper" 
>> >> strcast_func    "text" concat_pattern  "?||?"
>> >>  
>> >>  
>> >>  
>> >>  
>> >>  
>> >>  
>> >>  
>> >>  
>> >>  
>> >> my ldif
>> >>  
>> >>  
>> >> dn: dc=sql,dc=RU
>> >> objectclass: top
>> >> objectclass: dcObject
>> >> objectclass: organization
>> >> dc: sql
>> >> o: Sql Example
>> >> Description: Sql company
>> >>  
>> >> dn: cn:manager,dc=sql,dc=RU
>> >> objectclass: organizationalRole
>> >> cn: manager
>> >>  
>> >>  
>> >> and this what mysql.log trace
>> >>  
>> >> Jan 19 04:32:29 s90 slapd[1250]: conn=2 fd=9 ACCEPT from 
>> >> IP=127.0.0.1:36935 (IP=0.0.0.0:389)
>> >> Jan 19 04:32:29 s90 slapd[1319]: conn=2 op=0 BIND 
>> >> dn="cn=manager,dc=sql,dc=RU" method=128
>> >> Jan 19 04:32:29 s90 slapd[1319]: conn=2 op=0 BIND 
>> >> dn="cn=manager,dc=sql,dc=RU" mech=SIMPLE ssf=0
>> >> Jan 19 04:32:29 s90 slapd[1319]: conn=2 op=0 RESULT tag=97 err=0
>>  text=
>> >> Jan 19 04:32:29 s90 slapd[1318]: conn=2 op=1 ADD
>>  dn="dc=sql,dc=RU"
>> >> Jan 19 04:32:29 s90 slapd[1318]: conn=2 op=1 RESULT tag=105
>>  err=53 
>> >> text=operation not permitted within namingContext
>> >> Jan 19 04:32:29 s90 slapd[1319]: do_add: invalid dn 
>> >> (cn:manager,dc=sql,dc=RU)
>> >> Jan 19 04:32:29 s90 slapd[1319]: conn=2 op=2 RESULT tag=105
>>  err=34 
>> >> text=invalid DN
>> >> Jan 19 04:32:29 s90 slapd[1318]: conn=2 op=3 UNBIND
>> >> Jan 19 04:32:29 s90 slapd[1318]: conn=2 fd=9 close
>> >>  
>> >>  
>> >>  
>> >> Saluts Manuel
>> >
>> >
>> >
>> >-- 
>> >-----------------------------------
>> >Otto Kucera
>> >A-1020 Wien Engerthstrasse 137/6/7
>> >Tel: +43 699 1 942 30 91 [neue Nummer!]
>> >Email: ok@72pixel.at
>> >Icq: 65351173
>> >-----------------------------------
>> >
>> >And root said rm -rf /     ......and there was nothing
>> >
>> >Your mailserver MUST resolve properly (Fully Qualified Domain Name) or
>> the
>> >mail will not go through!
>> 
>> 
>> 
>> 
>> ---
>> You are currently subscribed to ldap@umich.edu as:
>> [Michael.Oberdorf@gmx.de]
>> To unsubscribe send email to ldap-request@umich.edu with the word
>> UNSUBSCRIBE as the SUBJECT of the message.
>> 
>
>
>---
>You are currently subscribed to ldap@umich.edu as: [mely@tm.minbas.cu]
>To unsubscribe send email to ldap-request@umich.edu with the word UNSUBSCRIBE as the SUBJECT of the message.