Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LDAP-37] Provide configuration for any-object attributes #15

Merged
merged 2 commits into from
Oct 2, 2023
Merged

[LDAP-37] Provide configuration for any-object attributes #15

merged 2 commits into from
Oct 2, 2023

Conversation

Sylinsic
Copy link
Contributor

@Sylinsic Sylinsic commented Oct 1, 2023

  • Allow configuration of name attribute for any-objects
  • Allow configuration of object classes for any-objects
  • Provide messages for the above mentioned config properties.

- Allow configuration of name attribute for any-objects
- Allow configuration of object classes for any-objects
- Provide messages for the above mentioned config properties.
@ilgrosso
Copy link
Member

ilgrosso commented Oct 2, 2023

Hi @Sylinsic thanks for this PR.

Could you please go ahead and open an issue on JIRA describing in detail your change?

Moreover, it would be good to add some test cases for the new feature, thank you.

Creating a 'device' object
@Sylinsic
Copy link
Contributor Author

Sylinsic commented Oct 2, 2023

Hi @ilgrosso,
I have added some test cases for the new methods.
Unfortunately, I'm unable to create an issue on Jira; I am unable to log in for whatever reason. If you are able to create one on my behalf as below that would be great!
"""
Title: Allow setting object classes and name attributes on any objects
Content: At present, it is not possible to configure the connector to set object classes or any name attributes of an any-object.
In the case that an any-object, such as a device or certificate, needs pushing, whilst the underlying LDAP server doesn't support the default configured attributes (i.e. entryUUID), then it is not possible to push to the underlying serer. Both object classes and name attributes should be configurable, as with users or groups, to allow pushing these objects to the LDAP server.
"""

@ilgrosso ilgrosso changed the title Provide configuration for any-object attributes [LDAP-37] Provide configuration for any-object attributes Oct 2, 2023
@ilgrosso
Copy link
Member

ilgrosso commented Oct 2, 2023

Unfortunately, I'm unable to create an issue on Jira; I am unable to log in for whatever reason. If you are able to create one on my behalf as below that would be great!

Sorry to hear that @Sylinsic
I went ahead and created https://connid.atlassian.net/browse/LDAP-37

Thank you again for your contribution.

@ilgrosso ilgrosso merged commit 427485b into Tirasa:master Oct 2, 2023
1 check passed
@Sylinsic
Copy link
Contributor Author

Sylinsic commented Oct 6, 2023

Hi @ilgrosso , I was wondering at what point the next maven build (1.5.8) would be published with this please?

@ilgrosso
Copy link
Member

ilgrosso commented Oct 7, 2023

Hi @Sylinsic not sure, but probably next month.
You can grab 1.5.8-SNAPSHOT from OSS Sonatype in the meantime.

@Sylinsic
Copy link
Contributor Author

Sylinsic commented Nov 5, 2023

Hi @ilgrosso, I'm really sorry to ask again, but my company's policy dictates that I am unable to use snapshot versions. With increasing pressure on me to deliver a product reliant on the updated version, I was hoping you could provide an updated timeline on when it will be released as a full version. Sorry for asking again!

@ilgrosso
Copy link
Member

ilgrosso commented Nov 6, 2023

I am proceeding with release 1.5.8 right now.

I invite you to subscribe to the ConnId User ML and to use that mean for further discussion and receive announcements on released artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants