[jira] [Commented] (DIRSERVER-2390) Index 0 out of bounds for length 0

2024-05-08 Thread David Paulsen (Jira) 


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

David Paulsen commented on DIRSERVER-2390:
--

OK thanks for the explanation! The apacheds-2.0.0.AM27.zip version is where I'm 
having the problem opening the connection in Studio. Since that's not really 
M28 that should be working, correct?

> Index 0 out of bounds for length 0
> --
>
> Key: DIRSERVER-2390
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2390
> Project: Directory ApacheDS
>  Issue Type: Bug
>Affects Versions: 2.0.0.AM27
>Reporter: Jürgen Weber
>Priority: Major
>
> On opening a connection from Directory Studio there is a error message
> An error has occurred. See error log for more details.
> Index 0 out of bounds for length 0
> eclipse.buildId=unknown
> java.version=11.0.21
> java.vendor=Eclipse Adoptium
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_DE
> Framework arguments:  /studio-rcp/resources/icons/linux/studio.xpm
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 
> /studio-rcp/resources/icons/linux/studio.xpm
> org.eclipse.ui.workbench
> Error
> Wed Jan 31 11:24:49 CET 2024
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.OverviewPage.refreshUI(OverviewPage.java:713)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.pageChanged(ServerConfigurationEditor.java:124)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart$5.run(MultiPageEditorPart.java:1231)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
>     at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.firePageChanged(MultiPageEditorPart.java:1228)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:834)
>     at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:501)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1032)
>     at 
> org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:612)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.hideLoadingPageAndDisplayConfigPages(ServerConfigurationEditor.java:421)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.configurationLoaded(ServerConfigurationEditor.java:370)
>     at 
> org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable$1.run(LoadConfigurationRunnable.java:144)
>     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
>     at 
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
>     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4001)
>     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3629)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
>     at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
>     at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
>     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
>     at org.apache.directory.studio.Application.start(Application.java:51)
>     at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>     at

[jira] [Commented] (DIRSERVER-2390) Index 0 out of bounds for length 0

2024-05-07 Thread David Paulsen (Jira) 


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

David Paulsen commented on DIRSERVER-2390:
--

What I really wanted is the AM27 version since it is released, but when I 
attempt to download apacheds-2.0.0.AM27.zip from from the link below it appears 
to contain the AM28 version. Is there a way to download the AM27 version? The 
AM27 version should work with Studio for configuration, correct?

[https://directory.apache.org/apacheds/downloads.html]

 

 

> Index 0 out of bounds for length 0
> --
>
> Key: DIRSERVER-2390
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2390
> Project: Directory ApacheDS
>  Issue Type: Bug
>Affects Versions: 2.0.0.AM27
>Reporter: Jürgen Weber
>Priority: Major
>
> On opening a connection from Directory Studio there is a error message
> An error has occurred. See error log for more details.
> Index 0 out of bounds for length 0
> eclipse.buildId=unknown
> java.version=11.0.21
> java.vendor=Eclipse Adoptium
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_DE
> Framework arguments:  /studio-rcp/resources/icons/linux/studio.xpm
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 
> /studio-rcp/resources/icons/linux/studio.xpm
> org.eclipse.ui.workbench
> Error
> Wed Jan 31 11:24:49 CET 2024
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.OverviewPage.refreshUI(OverviewPage.java:713)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.pageChanged(ServerConfigurationEditor.java:124)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart$5.run(MultiPageEditorPart.java:1231)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
>     at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.firePageChanged(MultiPageEditorPart.java:1228)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:834)
>     at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:501)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1032)
>     at 
> org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:612)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.hideLoadingPageAndDisplayConfigPages(ServerConfigurationEditor.java:421)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.configurationLoaded(ServerConfigurationEditor.java:370)
>     at 
> org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable$1.run(LoadConfigurationRunnable.java:144)
>     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
>     at 
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
>     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4001)
>     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3629)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
>     at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
>     at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
>     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
>     at org.apache.directory.studio.Application.start(Application.java:51)
>     at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
>

[jira] [Commented] (DIRSERVER-2390) Index 0 out of bounds for length 0

2024-04-30 Thread David Paulsen (Jira) 


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

David Paulsen commented on DIRSERVER-2390:
--

Can this be fixed? This is preventing us from using this release since we 
cannot open a configuration to configure partitions, etc.

> Index 0 out of bounds for length 0
> --
>
> Key: DIRSERVER-2390
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2390
> Project: Directory ApacheDS
>  Issue Type: Bug
>Affects Versions: 2.0.0.AM27
>Reporter: Jürgen Weber
>Priority: Major
>
> On opening a connection from Directory Studio there is a error message
> An error has occurred. See error log for more details.
> Index 0 out of bounds for length 0
> eclipse.buildId=unknown
> java.version=11.0.21
> java.vendor=Eclipse Adoptium
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_DE
> Framework arguments:  /studio-rcp/resources/icons/linux/studio.xpm
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 
> /studio-rcp/resources/icons/linux/studio.xpm
> org.eclipse.ui.workbench
> Error
> Wed Jan 31 11:24:49 CET 2024
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.OverviewPage.refreshUI(OverviewPage.java:713)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.pageChanged(ServerConfigurationEditor.java:124)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart$5.run(MultiPageEditorPart.java:1231)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
>     at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:174)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.firePageChanged(MultiPageEditorPart.java:1228)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:834)
>     at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:501)
>     at 
> org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1032)
>     at 
> org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:612)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.hideLoadingPageAndDisplayConfigPages(ServerConfigurationEditor.java:421)
>     at 
> org.apache.directory.studio.apacheds.configuration.editor.ServerConfigurationEditor.configurationLoaded(ServerConfigurationEditor.java:370)
>     at 
> org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable$1.run(LoadConfigurationRunnable.java:144)
>     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
>     at 
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
>     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4001)
>     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3629)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
>     at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
>     at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
>     at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
>     at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
>     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
>     at org.apache.directory.studio.Application.start(Application.java:51)
>     at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>     at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
>     at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
>     at

[jira] [Created] (DIRSERVER-2067) Password Policy Enforced for admin user

2015-06-01 Thread David Paulsen (JIRA) 
David Paulsen created DIRSERVER-2067:


 Summary: Password Policy Enforced for admin user
 Key: DIRSERVER-2067
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2067
 Project: Directory ApacheDS
  Issue Type: Bug
Affects Versions: 2.0.0-M20
Reporter: David Paulsen
Priority: Minor


When bound to a connection using the uid=admin,ou=system user, it enforces 
the ads-pwdInHistory in the password policy of the uid I'm changing the 
password for. For example, if I'm changing the password for 
uid=147547,ou=8300,ou=DVHead,dc=kewilltransport,dc=com, and that uid has a 
pwdPolicySubentry=ads-pwdId=DVHead8300,ou=passwordPolicies,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config,
 it enforces the ads-pwdId=DVHead8300 policy's ads-pwdInHistory setting even 
with the admin user.

My understanding is that since it's the admin user, it should not be enforcing 
any password policy rules.

Steps:
(1) Create a password policy where the ads-pwdInHistory is greater than 0 so it 
enforces not reusing passwords.
(2) Create a uid and set it's pwdPolicySubentry to the above password policy.
(3) Create a connection and bind to it using the uid=admin,ou=system user, 
and then modify password for the above uid. You will get this error:
error: invalid reuse of password present in password history




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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-05 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528368#comment-14528368
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Can I zip up the directory (containing the instance with renamed partition 
created below) and copy it to another M20 installation on Linux, or would I 
have to go through this procedure on the Linux box too?



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen
 Attachments: TMSInstance.zip


 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526597#comment-14526597
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Thanks!

I ran in to a problem trying to create a partition using Directory Studio 
version  2.0.0.v20130628. Steps:
(1) Install M20(on a Windows 7 laptop) and start the service.
(2) Start Directory Studio and create a connection configuration.
(3) Right click on my new connection configuration and choose Open 
Configuration. I get this error:
org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: 
ERR_04269 ATTRIBUTE_TYPE for OID ads-basedn does not exist!
at 
org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:293)
at 
org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:47)
at 
org.apache.directory.api.ldap.schemamanager.impl.DefaultSchemaManager.lookupAttributeTypeRegistry(DefaultSchemaManager.java:1604)
at 
org.apache.directory.api.ldap.model.entry.DefaultEntry.init(DefaultEntry.java:311)
at 
org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.readConfiguration(LoadConfigurationRunnable.java:359)
at 
org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.getConfiguration(LoadConfigurationRunnable.java:182)
at 
org.apache.directory.studio.apacheds.configuration.v2.jobs.LoadConfigurationRunnable.run(LoadConfigurationRunnable.java:127)
at 
org.apache.directory.studio.common.core.jobs.StudioJob.run(StudioJob.java:83)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.apache.directory.api.ldap.model.exception.LdapException: 
ERR_04269 ATTRIBUTE_TYPE for OID ads-basedn does not exist!
at 
org.apache.directory.api.ldap.model.schema.registries.DefaultSchemaObjectRegistry.lookup(DefaultSchemaObjectRegistry.java:176)
at 
org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:289)
... 8 more



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526618#comment-14526618
 ] 

David Paulsen commented on DIRSERVER-2051:
--

OK, a couple questions:
(1) Do you know when a the fixed version of Directory Studio will be released?
(2) What other tool could I use to create a partition with M20?



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526721#comment-14526721
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Is there any other lDAP tool or some command line tool to create partitions?



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Updated] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

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

David Paulsen updated DIRSERVER-2051:
-
Attachment: TMSInstance.zip

I've attached my M19 instance so you can translate it to M20. It's just the 
default instance with an empty partition called Kewill Transport added to it.



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen
 Attachments: TMSInstance.zip


 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527123#comment-14527123
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Could I use the default system partition instead of making my own. Is there any 
drawbacks/issues with doing that?



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen
 Attachments: TMSInstance.zip


 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527580#comment-14527580
 ] 

David Paulsen commented on DIRSERVER-2051:
--

OK, this is what I did and it seems to have worked:
(1) I started with the plain old default instance that gets created in install.
(2) Replace dc=example with dc=kewilltransport in the following files:
C:\apacheds\instances\default\conf\config.ldif_migrated (2 replacements)

C:\apacheds\instances\default\conf\ou=config\ads-directoryserviceid=default\ou=partitions\ads-partitionid=example.ldif
 (1 replacement)

C:\apacheds\instances\default\conf\ou=config\ads-directoryserviceid=default\ou=servers\ads-serverid=kerberosserver.ldif
 (1 replacement)
(2) Start server
(3) Add a context entry for dc=kewilltransport,dc=com as follows:
(a) Right click Root DSE and select New-New Context Entry
(b) Select Create from scratch
(c) Add Domain object class
(d) Enter dc=kewilltransport,dc=com
(e) Click Next, then Finish

Just to be sure, anything I create under the dc=kewilltransport,dc=com 
context entry will be in the example partition, correct?




 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen
 Attachments: TMSInstance.zip


 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-05-04 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527233#comment-14527233
 ] 

David Paulsen commented on DIRSERVER-2051:
--

I did that and then the {{dc=example,dc=com}} partition disappears completely 
in Directory Studio. 

Is there any way I can get the a version of Directory Studio that works with 
M20? 



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen
 Attachments: TMSInstance.zip


 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-27 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514286#comment-14514286
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Hello, do you have a new ETA for the M20 release? Was the release process 
started last week? Thanks.



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-20 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14503080#comment-14503080
 ] 

David Paulsen commented on DIRSERVER-2051:
--

I see that the ApacheDS web site still says M19. Any ETA on when it will be 
changed to M20? Thanks!



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-14 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494268#comment-14494268
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Thank you, that's great news!



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-14 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494238#comment-14494238
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Hi Kiran...

Do you know when M20 will be released?



 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-09 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487537#comment-14487537
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Just to be clear, the cases 1-3 I outlined above are the way it works today. 
You guys are the experts so I'll leave it to your judgement on what to do here. 
Our immediate need is to get the official 2.0.0-M20 release, with or without 
this change.

 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-08 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485450#comment-14485450
 ] 

David Paulsen commented on DIRSERVER-2051:
--

If all three cases had the same message I wouldn't be able to tell if the 
password was wrong or expired, so I'd rather leave it like it is.

 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-04-08 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485374#comment-14485374
 ] 

David Paulsen commented on DIRSERVER-2051:
--

FYI I'm using the Novell JLDAP API (not sure that bit of information is 
relevant here, but just in case).

Here are three cases that help describe the issue.

Case 1 (working as expected): 
If the password IS NOT expired, and I try to authenticate with the WRONG 
password, I get a com.novell.ldap.LDAPException with message:
INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user 
uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com

Case 2 (working as expected):
If the password IS expired, and I try to authenticate with the CORRECT 
password, I get a com.novell.ldap.LDAPException with message:
INVALID_CREDENTIALS: Bind failed: paasword expired

Case 3 (not working as expected):
If the password IS expired, and I try to authenticate with the WRONG password, 
I get a com.novell.ldap.LDAPException with message:
INVALID_CREDENTIALS: Bind failed: paasword expired

In Case 3, since the password I entered was wrong, I'm thinking it should 
return the values in Case 1. The thought being that information about the 
password being expired should not be disclosed if typing any old password value 
in. And logically it seems to me that the primary/first problem in Case 3 that 
the password is wrong, not that it's expired. Just my opinion.

By the way this is not a show-stopper issue for us, so from my perspective it 
doesn't have hold up the M20 release.


 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Commented] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-03-11 Thread David Paulsen (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRSERVER-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357550#comment-14357550
 ] 

David Paulsen commented on DIRSERVER-2051:
--

Can this make the 2.0.0-M20 release?

 Getting Password Expired Instead of Invalid Credentials
 ---

 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen

 When I log in with invalid credentials AND the password is expired, I 
 would expect to get the invalid credentials error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
 Cannot authenticate user 
 uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com
 Instead I get the password expired error:
 LDAPException: Invalid Credentials (49) Invalid Credentials
 LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
 expired
 I would think we should get the invalid credentials error in that case.



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

[jira] [Created] (DIRSERVER-2051) Getting Password Expired Instead of Invalid Credentials

2015-03-03 Thread David Paulsen (JIRA) 
David Paulsen created DIRSERVER-2051:


 Summary: Getting Password Expired Instead of Invalid Credentials
 Key: DIRSERVER-2051
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2051
 Project: Directory ApacheDS
  Issue Type: Bug
Reporter: David Paulsen


When I log in with invalid credentials AND the password is expired, I 
would expect to get the invalid credentials error:
LDAPException: Invalid Credentials (49) Invalid Credentials
LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: ERR_229 
Cannot authenticate user 
uid=admin,ou=DJPS1,ou=DVHead,dc=kewilltransport,dc=com

Instead I get the password expired error:
LDAPException: Invalid Credentials (49) Invalid Credentials
LDAPException: Server Message: INVALID_CREDENTIALS: Bind failed: paasword 
expired

I would think we should get the invalid credentials error in that case.




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