Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-28 Thread Abdala, Pablo Javier
Emmanuel and Kiran,
   Thank you very much for your 
time and help it has been much useful.
Kind Regards,

Pablo Javier Abdala




Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-24 Thread Abdala, Pablo Javier
Hello Emmanuel,
   First of all thanks a lot four your help, I can 
migrate from 1.5 to 2.0 and I can configured the Password Policy.

I have only one more doubt that I can´t solve looking on Internet. Regarding 
the password characteristics I can handle the long,  the duration and other 
item but I can't find the attribute to modify the pattern, for example the 
password must have at least 1 upperletter, 1 number and 1 special character 
(@#$%)). Can it be configured?

Thanks.

Kind Regards,

Pablo Abdala


Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-24 Thread Kiran Ayyagari
no currently it is not possible, please file a JIRA request so that we can
track it


On Fri, May 24, 2013 at 11:20 PM, Abdala, Pablo Javier
pablo.abd...@hp.comwrote:

 Hello Emmanuel,
First of all thanks a lot four your help, I
 can migrate from 1.5 to 2.0 and I can configured the Password Policy.

 I have only one more doubt that I can´t solve looking on Internet.
 Regarding the password characteristics I can handle the long,  the duration
 and other item but I can't find the attribute to modify the pattern, for
 example the password must have at least 1 upperletter, 1 number and 1
 special character (@#$%)). Can it be configured?

 Thanks.

 Kind Regards,

 Pablo Abdala




-- 
Kiran Ayyagari
http://keydap.com


Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-22 Thread Emmanuel Lécharny
Le 5/22/13 6:54 PM, Abdala, Pablo Javier a écrit :
 We don't provide installers for HP Unix, so you will have to use the
 archive tarball
 (http://directory.apache.org/apacheds/download/download-archive.html)

 Hello Emmanuel,
 I´ve installed the ApachedDS, then imported the schema from 
 1.5.3 but I had this error:
 #!RESULT ERROR
 #!CONNECTION ldap://dhpx0049:10389
 #!DATE 2013-05-22T12:07:52.469
 #!ERROR [LDAP: error code 68 - ENTRY_ALREADY_EXISTS: failed for MessageType : 
 ADD_REQUEST Message ID : 12 Add Request : Entry dn[n]: 
 dc=example,dc=com objectClass: domain objectClass: extensibleObject   
   objectClass: top dc: example : ERR_250_ENTRY_ALREADY_EXISTS 
 dc=example,dc=com already exists!]
 dn: dc=example,dc=com
 changetype: add
 dc: example
 objectClass: domain
 objectClass: extensibleObject
 objectClass: top

Plain normal. The example.com entry is already present by default.

 So I remove the Entry from the schema then imported again and I gave this 
 error:

 #!RESULT ERROR
 #!CONNECTION ldap://dhpx0049:10389
 #!DATE 2013-05-22T12:57:07.935
 #!ERROR [LDAP: error code 19 - CONSTRAINT_VIOLATION: failed for MessageType : 
 ADD_REQUEST Message ID : 50 Add Request : Entry dn[n]: 
 uid=z11,ou=users,dc=example,dc=com objectClass: person 
 objectClass: organizationalPerson objectClass: inetOrgPerson 
 objectClass: top uid: z11 sn: z11 userPassword: '0x70 
 0x65 0x70 0x65 ' cn: z11 displayName: z11 : Password should 
 have a minmum of 5 characters]
 dn: uid=z11,ou=users,dc=example,dc=com
 changetype: add
 displayName: z11
 objectClass: person
 objectClass: organizationalPerson
 objectClass: inetOrgPerson
 objectClass: top
 uid: z11

 Can you identify the problem?

Yes, the passwordPolicy is enabled, and it expect your password to be at
leat 5 chars long.

Either you modify your passowrd, or you disable the PasswordPolicy (but
I suspect you wanted to migrate because the PasswordPolicy is now
handled by 2.0...)


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 



Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-21 Thread Abdala, Pablo Javier
 we don't have a description of the migration procedure. However, we can
 drive you and help you to get 2.0 up and running.

 Could you provide some information about ;
 - your configuration (the server.xml file)
 - how many entries dyou have in your server
 - do you have any added schema elements ?

 Bottom line, the idea is to convert your configuration into something
that it usable for ApacheDS 2.0 (and you can configurate the server
using Studio), and to import your data into the server. If you have
created some AttributeTypes or ObjectClass, we will need to update the
schema.

 It should not be too complicated.

Thanks Emmanuel for your answer and your help.

Please find attached the server.xml file.
Regarding to entries  in server I've attached an example file

I don't understand your last question, do you have any added schema elements 
? could you clarify my?

Thanks in advance for your time an help.

Pablo Abdala


?xml version=1.0 encoding=UTF-8?

!--
  Licensed to the Apache Software Foundation (ASF) under one
  or more contributor license agreements.  See the NOTICE file
  distributed with this work for additional information
  regarding copyright ownership.  The ASF licenses this file
  to you under the Apache License, Version 2.0 (the
  License); you may not use this file except in compliance
  with the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing,
  software distributed under the License is distributed on an
  AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, either express or implied.  See the License for the
  specific language governing permissions and limitations
  under the License.
--


spring:beans xmlns:spring=http://xbean.apache.org/schemas/spring/1.0; 
			  xmlns:s=http://www.springframework.org/schema/beans;
			  xmlns=http://apacheds.org/config/1.0;

  defaultDirectoryService id=directoryService instanceId=default
   workingDirectory=example.com
   allowAnonymousAccess=true
   accessControlEnabled=false
   denormalizeOpAttrsEnabled=false
systemPartition
  !-- use the following partitionConfiguration to override defaults for --
  !-- the system partition  --
  jdbmPartition id=system cacheSize=100 suffix=ou=system optimizerEnabled=true syncOnWrite=true
indexedAttributes
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.1 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.2 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.3 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.4 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.5 cacheSize=10/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.6 cacheSize=10/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.7 cacheSize=10/
  jdbmIndex attributeId=ou cacheSize=100/
  jdbmIndex attributeId=uid cacheSize=100/
  jdbmIndex attributeId=objectClass cacheSize=100/
/indexedAttributes
contextEntry#systemContextEntry/contextEntry
!-- contextEntry
  s:value
objectClass: top
objectClass: organizationalUnit
objectClass: extensibleObject
ou: system
  /s:value
/contextEntry --
  /jdbmPartition
/systemPartition

partitions
  !-- NOTE: when specifying new partitions you need not include those   --
  !-- attributes below with OID's which are the system indices, if left --
  !-- out they will be automatically configured for you with defaults.  --
  jdbmPartition id=example cacheSize=100 suffix=dc=example,dc=com optimizerEnabled=true
 syncOnWrite=true
indexedAttributes
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.1 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.2 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.3 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.4 cacheSize=100/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.5 cacheSize=10/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.6 cacheSize=10/
  jdbmIndex attributeId=1.3.6.1.4.1.18060.0.4.1.2.7 cacheSize=10/
  jdbmIndex attributeId=dc cacheSize=100/
  jdbmIndex attributeId=ou cacheSize=100/
  jdbmIndex attributeId=krb5PrincipalName cacheSize=100/
  jdbmIndex attributeId=uid cacheSize=100/
  jdbmIndex attributeId=objectClass cacheSize=100/
/indexedAttributes
contextEntry#exampleContextEntry/contextEntry
!-- contextEntry
  s:value
objectClass: top
objectClass: domain
objectClass: extensibleObject

Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-21 Thread Emmanuel Lécharny
Le 5/21/13 5:31 PM, Abdala, Pablo Javier a écrit :
 we don't have a description of the migration procedure. However, we can
 drive you and help you to get 2.0 up and running.
 Could you provide some information about ;
 - your configuration (the server.xml file)
 - how many entries dyou have in your server
 - do you have any added schema elements ?
 Bottom line, the idea is to convert your configuration into something
 that it usable for ApacheDS 2.0 (and you can configurate the server
 using Studio), and to import your data into the server. If you have
 created some AttributeTypes or ObjectClass, we will need to update the
 schema.

 It should not be too complicated.
 Thanks Emmanuel for your answer and your help.

 Please find attached the server.xml file.
 Regarding to entries  in server I've attached an example file

I checked the server.xml file, it's a brand standard configuration. You
should be able to use ApacheDS 2.0 as is, inject you data, it should
work (it worked for me).



 I don't understand your last question, do you have any added schema elements 
 ? could you clarify my?

I just wanted to know if you have added some new schema elements, like
AttributeType or ObjectClass. Seems not.

So, bottom line : install apacheDS, import your data into it, you are
ready to go...

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 



Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-21 Thread Abdala, Pablo Javier
 I just wanted to know if you have added some new schema elements, like
AttributeType or ObjectClass. Seems not.

 So, bottom line : install apacheDS, import your data into it, you are
ready to go..

Ok, I will do what  you said, one more question, what file should I download to 
use Apache DS 2.0 in HP-UNIX?

Thanks,
Kind Regards,
Pablo Abdala


Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-21 Thread Emmanuel Lécharny
Le 5/21/13 9:19 PM, Abdala, Pablo Javier a écrit :
 I just wanted to know if you have added some new schema elements, like
 AttributeType or ObjectClass. Seems not.

 So, bottom line : install apacheDS, import your data into it, you are
 ready to go..

 Ok, I will do what  you said, one more question, what file should I download 
 to use Apache DS 2.0 in HP-UNIX?
We don't provide installers for HP Unix, so you will have to use the
archive tarball
(http://directory.apache.org/apacheds/download/download-archive.html)


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 



Re: Upgrade from ApacheDS 1.5.3 to 2.0

2013-05-17 Thread Emmanuel Lécharny
Le 5/17/13 10:36 PM, Abdala, Pablo Javier a écrit :
 Hello,
 I have Apache DS 1.5.3 in a server with HP-UX 11 and I need 
 to upgrade to 2.0 to be able to use Password Policy. I've toured the 
 http://directory.apache.org/apacheds/ page looking for information about 
 upgrade procedure but I couldn´t find anything, can you tell me where to find 
 information about upgrade procedure?
Hi,

we don't have a description of the migration procedure. However, we can
drive you and help you to get 2.0 up and running.

Could you provide some information about ;
- your configuration (the server.xml file)
- how many entries dyou have in your server
- do you have any added schema elements ?

Bottom line, the idea is to convert your configuration into something
that it usable for ApacheDS 2.0 (and you can configurate the server
using Studio), and to import your data into the server. If you have
created some AttributeTypes or ObjectClass, we will need to update the
schema.

It should not be too complicated.

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com