You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Gianmaria Clerici <gc...@bridgestream.com> on 2006/03/23 01:19:52 UTC
problems changing the admin user password with 0.9.3
I am starting the apache directory server with the default
configuration:
<prop key="java.naming.security.authentication">simple</prop>
<prop
key="java.naming.security.principal">uid=admin,ou=system</prop>
<prop key="java.naming.security.credentials">secret</prop>
But then I would like to change the password for the admin user.
I log into the apache server with an LDAP browser and change the
password to "newpassword".
Then I shutdown the server and change the configuration:
<prop key="java.naming.security.authentication">simple</prop>
<prop
key="java.naming.security.principal">uid=admin,ou=system</prop>
<prop key="java.naming.security.credentials">newpassword</prop>
I get an error as the SimpleAuthenticator is failing.
If I use "secret" again, it works.
So how do I change the admin password, permanently?
Re: MINA broadcast support
Posted by Jörg Henne <j....@levigo.de>.
Alex Karasulu schrieb:
> Trustin Lee wrote:
>> Niklas already answered, but I'd like to comment a little bit more.
>>
>> On 3/23/06, *Jörg Henne* <j.henne@levigo.de
>> <ma...@levigo.de>> wrote:
>>
>> the MINA website lists (UDP) broadcast support as missing. Is this
>> information still correct? Do you have any pointers for me, if I
>> were to
>> embark on a mission to build broadcast support (specifically,
>> something
>> DHCPish) based on old IO?
>>
>>
>> It's still correct and we'll be really glad if someone wants to
>> implement it. Implementing a new transport type ( i.e. multicast) is
>> to implement IoAcceptor and IoConnector interface. Please refer to
>> the implementation classes such as DatagramAcceptor and
>> DatagramConnector.
>>
>> I didn't consider broadcasting at the moment I designed MINA API, so
>> you might have to modify the API to support broadcasting thoroughly.
>> It's OK of course. I think we need to support multicast before we
>> release 1.0 for the completeness of the API.
>
> Agreed would be nice to have multicast for DHCP server implementation
> within ApacheDS soon so development on that can continue. This is a
> big wish :).
>
> Alex
>
Thanks to all for your input. I'll hopefully find time to have a look at
this stuff some time next week. But don't hold your breath for a fully
functioning DHCP server :-/
Joerg Henne
Re: MINA broadcast support
Posted by Alex Karasulu <ao...@bellsouth.net>.
Trustin Lee wrote:
> Niklas already answered, but I'd like to comment a little bit more.
>
> On 3/23/06, *Jörg Henne* <j.henne@levigo.de
> <ma...@levigo.de>> wrote:
>
> the MINA website lists (UDP) broadcast support as missing. Is this
> information still correct? Do you have any pointers for me, if I
> were to
> embark on a mission to build broadcast support (specifically,
> something
> DHCPish) based on old IO?
>
>
> It's still correct and we'll be really glad if someone wants to
> implement it. Implementing a new transport type ( i.e. multicast) is
> to implement IoAcceptor and IoConnector interface. Please refer to
> the implementation classes such as DatagramAcceptor and DatagramConnector.
>
> I didn't consider broadcasting at the moment I designed MINA API, so
> you might have to modify the API to support broadcasting thoroughly.
> It's OK of course. I think we need to support multicast before we
> release 1.0 for the completeness of the API.
Agreed would be nice to have multicast for DHCP server implementation
within ApacheDS soon so development on that can continue. This is a big
wish :).
Alex
Re: MINA broadcast support
Posted by Trustin Lee <tr...@gmail.com>.
Niklas already answered, but I'd like to comment a little bit more.
On 3/23/06, Jörg Henne <j....@levigo.de> wrote:
>
> the MINA website lists (UDP) broadcast support as missing. Is this
> information still correct? Do you have any pointers for me, if I were to
> embark on a mission to build broadcast support (specifically, something
> DHCPish) based on old IO?
It's still correct and we'll be really glad if someone wants to implement
it. Implementing a new transport type (i.e. multicast) is to implement
IoAcceptor and IoConnector interface. Please refer to the implementation
classes such as DatagramAcceptor and DatagramConnector.
I didn't consider broadcasting at the moment I designed MINA API, so you
might have to modify the API to support broadcasting thoroughly. It's OK of
course. I think we need to support multicast before we release 1.0 for the
completeness of the API.
HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
Re: DHCP support in DS, was: Re: MINA broadcast support
Posted by Enrique Rodriguez <en...@gmail.com>.
On 3/28/06, Jörg Henne <j....@levigo.de> wrote:
> without digging deep into the Kerberos et al. implementations: how does
> communication between the protocol implementations and the directory
> work? Do the protocols bind to the directory like ordinary clients or is
> there an in-VM backdoor?
Protocols bind like ordinary JNDI clients, using an in-VM JNDI
context. The key item here is the proper Initial Context Factory to
use that accesses the JNDI provider without going over the wire. This
is the "CoreContextFactory":
DEFAULT_INITIAL_CONTEXT_FACTORY =
"org.apache.directory.server.core.jndi.CoreContextFactory";
Usage is something like this (some interpretation required):
private InitialContextFactory factory;
private Hashtable env;
env = new Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, DEFAULT_INITIAL_CONTEXT_FACTORY );
env.put( Context.PROVIDER_URL, "ou=DhcpStuff,dc=example,dc=com" );
try
{
DirContext ctx = ( DirContext ) factory.getInitialContext( env );
}
... etc.
Enrique
DHCP support in DS, was: Re: MINA broadcast support
Posted by Jörg Henne <j....@levigo.de>.
Hi,
Enrique Rodriguez wrote:
>
> 2) There is no JNDI-backed store impl. The schema is in the ApacheDS
> core, ready-to-go.
without digging deep into the Kerberos et al. implementations: how does
communication between the protocol implementations and the directory
work? Do the protocols bind to the directory like ordinary clients or is
there an in-VM backdoor?
Joerg Henne
Re: MINA broadcast support
Posted by Alex Karasulu <ao...@bellsouth.net>.
Enrique Rodriguez wrote:
> Jörg Henne wrote:
>> Enrique Rodriguez schrieb:
> ...
>>> Our Apache DHCP provider work is stalled because of lack of
>>> broadcast support in MINA. I would love to see broadcast support in
>>> MINA so I encourage any contributions in this area, if you are able.
>>>
>>> Enrique
>> Ok, sounds good. What exactly does "stalled" mean? Is there already
>> something in the general direction of handling DHCP packet
>> encoding/decoding to start with? That would be quite interesting for
>> me, since what I'm trying to achieve is a special kind of DHCP
>> server. Making it a general one wouldn't be to hard from there.
>
> The DHCP protocol provider work is in the Directory repo at:
>
> https://svn.apache.org/repos/asf/directory/trunks/apacheds/protocol-dhcp/
>
> The codecs work and the handler will reply with a static response. I
> think all of the 2 primary RFC's (2131, 2132) are wired in, w.r.t.
> DHCP options. Caveats are that the MINA version is ancient and I'm
> not sure how well the code survived the update to Maven M2.
Well the survival seems to be good all test cases have passed but
there's only approximately two test cases in the module. Perhaps Jorg
can start off by adding more test cases as he gets more familiar with
the code to flesh out whats working and what is not. It would be great
to have any help at all on the DHCP server along with support for multicast.
...
> P.S. DNS is in a similar boat. Basic serving works and is even
> up-to-date w.r.t. JNDI store and OSGi. We've just stalled more DNS
> documentation and support since we really want to get to Dynamic DNS,
> which requires DHCP, which requires broadcast ...
It will be a great day when all these services start working in tandem.
Alex
Re: MINA broadcast support
Posted by Enrique Rodriguez <en...@gmail.com>.
Jörg Henne wrote:
> Enrique Rodriguez schrieb:
...
>> Our Apache DHCP provider work is stalled because of lack of broadcast
>> support in MINA. I would love to see broadcast support in MINA so I
>> encourage any contributions in this area, if you are able.
>>
>> Enrique
> Ok, sounds good. What exactly does "stalled" mean? Is there already
> something in the general direction of handling DHCP packet
> encoding/decoding to start with? That would be quite interesting for me,
> since what I'm trying to achieve is a special kind of DHCP server.
> Making it a general one wouldn't be to hard from there.
The DHCP protocol provider work is in the Directory repo at:
https://svn.apache.org/repos/asf/directory/trunks/apacheds/protocol-dhcp/
The codecs work and the handler will reply with a static response. I
think all of the 2 primary RFC's (2131, 2132) are wired in, w.r.t. DHCP
options. Caveats are that the MINA version is ancient and I'm not sure
how well the code survived the update to Maven M2. I don't think the
code has been touched in over a year.
For the record, there are a couple enhancements this impl needs:
1) There is absolutely no workflow, meaning that currently the service
will reply with a static OFFER response. Only when I tried getting
broadcast working, to start coding in the protocol workflow, did I
release there was no broadcast support so I backburnered it.
2) There is no JNDI-backed store impl. The schema is in the ApacheDS
core, ready-to-go.
3) All of the other protocols support some level of OSGi, either basic
plugability or full dynamic reconfiguration using OSGi and DIT-backed
config using the OSGi Config Admin service.
#2 and #3 should be straightforward; been done numerous times. This
code has just not been kept up with the other protocols. Just blocked
by lack of broadcast. I'd love to get back in and update and maintain
once broadcast is available.
Enrique
P.S. DNS is in a similar boat. Basic serving works and is even
up-to-date w.r.t. JNDI store and OSGi. We've just stalled more DNS
documentation and support since we really want to get to Dynamic DNS,
which requires DHCP, which requires broadcast ...
Re: MINA broadcast support
Posted by Jörg Henne <j....@levigo.de>.
Enrique Rodriguez schrieb:
> Niklas Therning wrote:
> ...
>> AFAIK broadcast is not supported in MINA at the moment.
> ...
>> Jörg Henne wrote:
>>> Hi all,
>>>
>>> the MINA website lists (UDP) broadcast support as missing. Is this
>>> information still correct? Do you have any pointers for me, if I
>>> were to embark on a mission to build broadcast support
>>> (specifically, something DHCPish) based on old IO?
>
> Our Apache DHCP provider work is stalled because of lack of broadcast
> support in MINA. I would love to see broadcast support in MINA so I
> encourage any contributions in this area, if you are able.
>
> Enrique
Ok, sounds good. What exactly does "stalled" mean? Is there already
something in the general direction of handling DHCP packet
encoding/decoding to start with? That would be quite interesting for me,
since what I'm trying to achieve is a special kind of DHCP server.
Making it a general one wouldn't be to hard from there.
Joerg Henne
Re: MINA broadcast support
Posted by Enrique Rodriguez <en...@gmail.com>.
Niklas Therning wrote:
...
> AFAIK broadcast is not supported in MINA at the moment.
...
> Jörg Henne wrote:
>> Hi all,
>>
>> the MINA website lists (UDP) broadcast support as missing. Is this
>> information still correct? Do you have any pointers for me, if I were
>> to embark on a mission to build broadcast support (specifically,
>> something DHCPish) based on old IO?
Our Apache DHCP provider work is stalled because of lack of broadcast
support in MINA. I would love to see broadcast support in MINA so I
encourage any contributions in this area, if you are able.
Enrique
Re: MINA broadcast support
Posted by Niklas Therning <ni...@trillian.se>.
Hi Jörg,
AFAIK broadcast is not supported in MINA at the moment.
BTW, MINA related questions are best asked on the MINA developers list.
http://directory.apache.org/subprojects/mina/mail-lists.html describes
how to subscribe. I'm forwarding your question below to that list.
HTH
/Niklas
Jörg Henne wrote:
> Hi all,
>
> the MINA website lists (UDP) broadcast support as missing. Is this
> information still correct? Do you have any pointers for me, if I were to
> embark on a mission to build broadcast support (specifically, something
> DHCPish) based on old IO?
>
> Thanks
> Joerg Henne
Re: MINA broadcast support
Posted by Niklas Therning <ni...@trillian.se>.
Hi Jörg,
AFAIK broadcast is not supported in MINA at the moment.
BTW, MINA related questions are best asked on the MINA developers list.
http://directory.apache.org/subprojects/mina/mail-lists.html describes
how to subscribe. I'm forwarding your question below to that list.
HTH
/Niklas
Jörg Henne wrote:
> Hi all,
>
> the MINA website lists (UDP) broadcast support as missing. Is this
> information still correct? Do you have any pointers for me, if I were to
> embark on a mission to build broadcast support (specifically, something
> DHCPish) based on old IO?
>
> Thanks
> Joerg Henne
MINA broadcast support
Posted by Jörg Henne <j....@levigo.de>.
Hi all,
the MINA website lists (UDP) broadcast support as missing. Is this
information still correct? Do you have any pointers for me, if I were to
embark on a mission to build broadcast support (specifically, something
DHCPish) based on old IO?
Thanks
Joerg Henne
Re: problems changing the admin user password with 0.9.3
Posted by Alex Karasulu <ao...@bellsouth.net>.
Switch to RC1. Might be a bug which is fixed already. We cannot support
earlier branches of development along with 1.0 and 1.1 in the trunk.
Excuse the inconvenience.
Alex
Gianmaria Clerici wrote:
>
> I am starting the apache directory server with the default configuration:
>
> <prop key="java.naming.security.authentication">simple</prop>
>
> <prop key="java.naming.security.principal">uid=admin,ou=system</prop>
>
> <prop key="java.naming.security.credentials">secret</prop>
>
> But then I would like to change the password for the admin user.
>
> I log into the apache server with an LDAP browser and change the
> password to “newpassword”.
>
> Then I shutdown the server and change the configuration:
>
> <prop key="java.naming.security.authentication">simple</prop>
>
> <prop key="java.naming.security.principal">uid=admin,ou=system</prop>
>
> <prop key="java.naming.security.credentials">newpassword</prop>
>
> I get an error as the SimpleAuthenticator is failing.
>
> If I use “secret” again, it works.
>
> So how do I change the admin password, permanently?
>
>