[jira] [Resolved] (DIRSERVER-2076) Migration from M19 to M20 fails due to new attribute ads-baseDn on authenticators

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-2076.
------------------------------------------
    Resolution: Later

I have created DIRSERVER-2077 to follow this migration problem.

> Migration from M19 to M20 fails due to new attribute ads-baseDn on authenticators
> ---------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-2076
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2076
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M20
>            Reporter: lucas theisen
>         Attachments: default.tgz, default_with_ads-baseDn.tgz
>
>
> When migrating from {{2.0.0-M19}} to {{2.0.0-M20}} the config migration fails with this exception:
> {code}
> [13:28:32] DEBUG [org.apache.directory.server.config.ConfigPartitionReader] - The top level object class is ads-authenticatorImpl
> [13:28:32] DEBUG [org.apache.directory.server.config.ConfigPartitionReader] - Bean org.apache.directory.server.config.beans.AuthenticatorImplBean created for ObjectClass ads-authenticatorImpl
> [13:28:32] ERROR [org.apache.directory.server.config.ConfigPartitionReader] - No value was configured for entry with DN 'ads-authenticatorId=simpleauthenticator,ou=authenticators,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config' and attribute type 'ads-baseDn'.
> org.apache.directory.server.config.ConfigurationException: No value was configured for entry with DN 'ads-authenticatorId=simpleauthenticator,ou=authenticators,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config' and attribute type 'ads-baseDn'.
>         at org.apache.directory.server.config.ConfigPartitionReader.readFieldValue(ConfigPartitionReader.java:472)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:631)
>         at org.apache.directory.server.config.ConfigPartitionReader.read(ConfigPartitionReader.java:535)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:644)
>         at org.apache.directory.server.config.ConfigPartitionReader.read(ConfigPartitionReader.java:535)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:644)
>         at org.apache.directory.server.config.ConfigPartitionReader.read(ConfigPartitionReader.java:535)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:768)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:732)
>         at org.apache.directory.server.config.ConfigPartitionReader.readConfig(ConfigPartitionReader.java:704)
>         at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:177)
>         at org.apache.directory.server.UberjarMain.start(UberjarMain.java:76)
>         at org.apache.directory.server.UberjarMain.main(UberjarMain.java:54)
> {code}
> So, I figured I could try adding that attribute in before migration, but then it fails with this exception:
> {code}
> [13:37:02] INFO [org.apache.directory.server.config.ConfigPartitionInitializer] - Old config partition detected, converting to multiple LDIF file configuration model
> java.util.NoSuchElementException: ERR_04269 ATTRIBUTE_TYPE for OID ads-basedn does not exist!
>         at org.apache.directory.api.ldap.model.ldif.LdifReader.nextInternal(LdifReader.java:1897)
>         at org.apache.directory.api.ldap.model.ldif.LdifReader.next(LdifReader.java:1920)
>         at org.apache.directory.server.config.ConfigPartitionInitializer.initConfigPartition(ConfigPartitionInitializer.java:155)
>         at org.apache.directory.server.ApacheDsService.initConfigPartition(ApacheDsService.java:289)
>         at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:172)
>         at org.apache.directory.server.UberjarMain.start(UberjarMain.java:76)
>         at org.apache.directory.server.UberjarMain.main(UberjarMain.java:54)
> {code}
> This appears to be leaving me in a chicken/egg type scenario...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)