You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Shawn McKinney <sm...@apache.org> on 2021/07/04 15:48:40 UTC
[ STUDIO ] Problem viewing / setting configuration
Hi,
Trying to get LDAPS configured on ApacheDS version 2.0.0.AM26 using Studio version 2.0.0.v20210213-M16.
This on an Ubuntu20 w/ openjdk version 11.0.11.
I connect to the server instance and open configuration dialog and get this:
ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist
Full error[1] listed below.
When I open the schema browser, I find that the specified attribute type defined.
The fortress integration tests have also been run on this instance providing verification that its schema is valid.
Any ideas on what this problem is?
Thanks,
—
Shawn
[1] Unable to load the configuration.
- ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
at org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:316)
at org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:50)
at org.apache.directory.api.ldap.schema.manager.impl.DefaultSchemaManager.lookupAttributeTypeRegistry(DefaultSchemaManager.java:1831)
at org.apache.directory.api.ldap.model.entry.DefaultEntry.<init>(DefaultEntry.java:320)
at org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable.readConfiguration(LoadConfigurationRunnable.java:407)
at org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable.getConfiguration(LoadConfigurationRunnable.java:198)
at org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable.run(LoadConfigurationRunnable.java:136)
at org.apache.directory.studio.common.core.jobs.StudioJob.run(StudioJob.java:85)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.directory.api.ldap.model.exception.LdapException: ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
at org.apache.directory.api.ldap.model.schema.registries.DefaultSchemaObjectRegistry.lookup(DefaultSchemaObjectRegistry.java:259)
at org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:312)
... 8 more
ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [ STUDIO ] Problem viewing / setting configuration
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 4, 2021, at 11:34 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> This method loads the config from the "ou=config" partition by fetching
> all entries within this partition. It seems some entry in this partition
> contains a "ftmodcode" attribute. I think that's not supported, the
> config reader expects that only ApacheDS config schema elements are used
> (AT and OC with an "ads-" prefix). How did the ftmodcode attribute get
> there?
Ah yes that was it. The fortress integration tests add a set of pw policies. All entries added will include some attributes from an aux object class, used for tracking stuff.
Never realized it was a problem until now.
Might need to rethink how to add policies to ADS.
In the meantime, you got me past this problem.
Thanks Stefan
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org
Re: [ STUDIO ] Problem viewing / setting configuration
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 7/4/21 5:48 PM, Shawn McKinney wrote:
> Hi,
>
> Trying to get LDAPS configured on ApacheDS version 2.0.0.AM26 using Studio version 2.0.0.v20210213-M16.
>
> This on an Ubuntu20 w/ openjdk version 11.0.11.
>
> I connect to the server instance and open configuration dialog and get this:
>
> ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist
>
> Full error[1] listed below.
>
> When I open the schema browser, I find that the specified attribute type defined.
>
> The fortress integration tests have also been run on this instance providing verification that its schema is valid.
>
> Any ideas on what this problem is?
>
> Thanks,
>
> —
> Shawn
>
> [1] Unable to load the configuration.
> - ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
> org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: ERR_13735_ELEMENT_FOR_OID_DOES_NOT_EXIST ATTRIBUTE_TYPE for OID ftmodcode does not exist!
> at org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:316)
> at org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:50)
> at org.apache.directory.api.ldap.schema.manager.impl.DefaultSchemaManager.lookupAttributeTypeRegistry(DefaultSchemaManager.java:1831)
> at org.apache.directory.api.ldap.model.entry.DefaultEntry.<init>(DefaultEntry.java:320)
> at org.apache.directory.studio.apacheds.configuration.jobs.LoadConfigurationRunnable.readConfiguration(LoadConfigurationRunnable.java:407)
This method loads the config from the "ou=config" partition by fetching
all entries within this partition. It seems some entry in this partition
contains a "ftmodcode" attribute. I think that's not supported, the
config reader expects that only ApacheDS config schema elements are used
(AT and OC with an "ads-" prefix). How did the ftmodcode attribute get
there?
Kind Regards,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org