Re: incorrect pattern ?

[Emmanuel Lécharny]

Le 26/01/16 09:10, Blangille Denis a écrit :
> Hello,
>
> i'm sorry to be incomprehensible.
>
> When i talk about 'pattern', this is apacheds schema's.

What LDAP schema are you using ?

In any case, with Studio, you should be able to connect on the server
and check the loaded schemas, to see if the radius one is there.

> Actually, i try to link apacheds ldap server(M 20) with a radius server 
> (freeradius v3.04)
> When i run the radius server in debug mode and after the bind is successful, 
> apacheds send a connection reset.
We need some logs here. There are so many possible cause for such an
error...

Try to be explicit and exhaustive, instead of providing fragment of
informations about what you are trying to do and how you do it. It's
impossible for us to give you some help otherwise !

Re: incorrect pattern ?

[Blangille Denis]

Hello,

i'm sorry to be incomprehensible.

When i talk about 'pattern', this is apacheds schema's.
Actually, i try to link apacheds ldap server(M 20) with a radius server 
(freeradius v3.04)
When i run the radius server in debug mode and after the bind is successful, 
apacheds send a connection reset.

Sincerely.

Denis

Le Lundi 25 Janvier 2016 19:56 CET, Emmanuel Lécharny  a 
écrit:

> Le 25/01/16 19:44, Blangille Denis a écrit :
> > Hello,
> Hi,
> >
> > How can i verify if a imported pattern is correct ? This is to link 
> > apacheds and freeradius server.
> > Is a pattern for openldap works with apacheds ? Because freeradius server 
> > provides this pattern.
>
> Can you be a bit more explicit about whatyou call a 'pattern' ?
> Actually, a full description of what you are trying to do would be useful.
>
> Thanks !
>

Re: DHCP using Apache directory server

[Sherman Lilly]

Can I fix the schema in my current version 2.0.0? If so how do I do this?

On Wed, Jan 20, 2016 at 7:04 PM, Emmanuel Lécharny 
wrote:

> Le 20/01/16 23:16, Stefan Seelmann a écrit :
> > On 01/19/2016 02:46 PM, Sherman Lilly wrote:
> >> I have got my schemas installed and working and the directory server is
> >> working properly. I am trying to add a value to "dhcpOption" and it will
> >> only accept a binary value. I figured out the value has to be utf8
> encoded
> >> value. How do I use Directory Studio to insert this value? Let say the
> >> string is "broadcast 192.168.255.255". Not really sure how to convert
> that
> >> to utf8 encoded binary and insert it into "dhcpOption" thorugh Directory
> >> Studio.
> >>
> >> Any help is appreciated.
> > First I have to tell you that the DHCP (and also DNS) servers are not
> > maintained since years, I not even can find any server-side integration
> > test that tests the functionality. So very likely those won't work at
> > all or include major bugs. Help to test, fix, and document is however
> > appreciated :)
>
> indeed...
> >
> > I just tried to add a "dhcpOption" value with Studio. As this attribute
> > is of syntax octet string the Hex Editor opens. I then choosed the "Edit
> > as Text" option. The resulting binary is a proper UTF-8 encoded value.
> > But when saving that there is an error on server side, I think that is a
> > bug in the LDAP API.
>
> No, it's a bug in the schema definition. I think we took it from
> https://www.ietf.org/proceedings/53/I-D/draft-ietf-dhc-ldap-schema-00.txt,
> where it says :
>
> ( 2.16.840.1.113719.1.203.4.7
>   NAME 'dhcpOption'
>   DESC 'Encoded optio values to be sent to clients.  Each value represents
> a single option and contains (OptionTag, Length, OptionValue) encoded in
> the format used by DHCP.'
>   SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
>
> Our definition is slightly different :
>
> attributetype ( 2.16.840.1.113719.1.203.4.7
> NAME 'dhcpOption'
> DESC 'Encoded option values to be sent to clients. Each value
> represents a single option and contains (OptionTag, Length, OptionValue)
> encoded in the format used by DHCP.'
> EQUALITY caseIgnoreIA5Match
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
>  )
>
> The pb is that using a caseIgnoreIA5Match matching rule for a OCTET STRING
> syntax is simply not working, and leads to an error when we try to inject a
> dhcpOption in the server.
>
>
> The only way to get this fixed would be to fix the schema, and use a
> 1.3.6.1.4.1.1466.115.121.1.26 Syntax (IA5String).
>
> We can do that...
>
>

Re: DHCP using Apache directory server

[Stefan Seelmann]

On 01/26/2016 07:56 PM, Sherman Lilly wrote:
> Can I fix the schema in my current version 2.0.0? If so how do I do this?

Yes, you can change the syntax of dhcpOption attribute, e.g. you can
apply the following LDIF:

dn: m-oid=2.16.840.1.113719.1.203.4.7,
 ou=attributeTypes,cn=dhcp,ou=schema
changetype: modify
replace: m-syntax
m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
-

Afterwards you need to restart the server.

HTH,
Stefan