Plea for a new release

[a1730]

Motivation

The LLDAP team has added some very useful enhancements to LLDAP since the v0.5.0 release that users like myself would like to be able to use. A recent point in case is the case-insensitive additions. make attributes names, group names and emails case insensitive

Describe the solution you'd like
Please, pretty please, release a new build on Linux AMD64 for us rusted amateurs.

Describe alternatives you've considered

• I tried unsuccessfully to do a local build because rust keeps crashing on my DEBIAN 12 vm running on SmartOS hypervisor during compilation. I do not wish to learn rust language just to be able to compile LLDAP. OpenLDAP compiles but I lost the fight to slapd and his friends.
• I do not run docker but typically will download the image and extract the artifact until they started with this OCI wrapper, and the download script started failing with error: unknown manifest mediaType (lldap/lldap:lldap/lldap@latest): 'application/vnd.oci.image.index.v1+json' which is a battle for another day.

Basically, I'm stuck.

Additional context
I cannot thank you enough for this project.

[martadinata666]

The problem with the second issue manifest error is that you need a newer docker version, 24+ is a must.

Or you can take binary artifacts directly from GitHub actions pipelines such as here https://github.com/lldap/lldap/actions/runs/7449328497

[nitnelave]

A release is in the works! There's just one final bug I want to squash (#763) before doing a release, and I'm also waiting for ldap3_proto to release a fix they made for us. You can expect a release probably next week or the one after.

[a1730]

The problem with the second issue manifest error is that you need a newer docker version, 24+ is a must.

Or you can take binary artifacts directly from GitHub actions pipelines such as here https://github.com/lldap/lldap/actions/runs/7449328497

Just what the doctor orderd. I cannot thank you enough!

[pixelrazor]

I'm also just cracking at ui pages for user defined attributes - I'm not sure where that should fall WRT a release, but if that's important for you, maybe it can make it to a release

[gcamblin]

I'd like to add my voice for the user-defined attributes feature. I've got a use case where it would be great to add an SSH-keys attribute.

[nitnelave]

You know, we have daily tagged docker releases, you can always grab today's one and stick to it until the next release. That's "stable" :)

There are no known serious bugs in today's release (2024-02-08 I think?) And it has the user defined attributes. It's not a full release because the web UI for it is halfway there: you don't see the values of the attributes in the user details.

[gcamblin]

Thank you for the recommendation on using the daily tagged Docker releases. I've already been working with the 2024-02-08 build and am pleased to confirm that the issue with the getDetails rendering loop has been resolved.

I've also begun experimenting with adding custom attributes. However, after successfully adding a custom user attribute for SSH keys, I noticed that this new attribute doesn't appear in the form for adding new users. This prevents the assignment of any value to the attribute. Given that the web UI for managing these attributes is still under development, is there an alternative method for assigning values to these custom attributes in the meantime?

[nitnelave]

That's why it's not a stable release ;) There's https://github.com/Zepmann/lldap-cli that you can use to manipulate custom attributes (both creation and setting new values).

…

On Fri, Feb 9, 2024 at 4:54 PM Gary Camblin ***@***.***> wrote: Thank you for the recommendation on using the daily tagged Docker releases. I've already been working with the 2024-02-08 build and am pleased to confirm that the issue with the getDetails rendering loop has been resolved. I've also begun experimenting with adding custom attributes. However, after successfully adding a custom user attribute for SSH keys, I noticed that this new attribute doesn't appear in the form for adding new users. This prevents the assignment of any value to the attribute. Given that the web UI for managing these attributes is still under development, is there an alternative method for assigning values to these custom attributes in the meantime? — Reply to this email directly, view it on GitHub <#790 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGCPWNWPB55YMECON6L7MTYSZBBZAVCNFSM6AAAAABBYLQOQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGE3TENZSGY> . You are receiving this because you commented.Message ID: ***@***.***>

-- Valentin Tolmer

[pixelrazor]

Also, there's the /API/graphql/playground endpoint where you can send the graphql mutation for update user to set the values. I'm in the middle of the user details page changes right now to view and change them, I'm HOPING to have time to get it out for review this coming week, the. The group attributes will be right behind it

[onedr0p]

Any update on if/when a new release will be made? 🙏🏼

[nitnelave]

As soon as the frontend is ready! Work is in progress.

[Aeris1One]

Hi, is there any plan for the release ?
Deseperately waiting on a release to add custom attribute to a production server (as of now the "last_name" attribute is used to store the Google OIDC sub id 😅)

[nitnelave]

It's currently blocked on being able to set values to custom attributes from the frontend. Currently you can create attributes, but not set values. You can only do that through LDAP, the GraphQL API or lldap-cli.

Once that's in, I'll make a release. The current state is just too confusing for users who are not aware of it.

Apart from that, you can grab the latest release (or a dated release) and it'll have the same features!