directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Warren Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-2076) Migration from M19 to M20 fails due to new attribute ads-baseDn on authenticators
Date Wed, 23 Aug 2017 02:29:00 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137777#comment-16137777
] 

Warren Rogers commented on DIRSERVER-2076:
------------------------------------------

I came across this issue also with M24.

After some troubleshooting, and not being able to use this workaround, I finally found the
problem.

The *config.ldif* has the attribute *ads-baseDn* with the value of " " (space).

The config.ldif conversion works perfectly with the space, but if that space is removed so
that the attribute reads just *ads-baseDn:* the conversion fails.

So, how did the exported file have those spaces removed?  My IDE (JetBrains Idea) is set to
clean extra whitespace from files, for size and general cleanliness.  Thus, the working file
now fails with my new directory server vs the directory server I created via Apache Studio,
which I used to export the *config.ldif*.

So, I would say this is still a bug.  Values of attributes should be allowed non-space, or
no value.  Or, require non-value attributes be some other value, such as 'null'  If 'null'
is not allowable, then the reader should add the space during initialization.

> 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.4.14#64029)

Mime
View raw message