nitnelave

Piggy-backing on this question, but it's related: Is there an easy way to model the implicit vs explicit null in a query, like https://graphql-rust.github.io/juniper/master/advanced/implicit_and_explicit_null.html ? Basically, I'd like to be...

(and in the README)

Sorry, I'm cringing a bit reading the code I wrote more than 5 years ago... In your config.yml, if you write: ```yml sound: type: "BLOCK_CHORUS_FLOWER_GROW" ``` Does it work? I...

Then sorry, maybe the API changed since? Or there's a bug in the code. I haven't touched this project in a long time, I'm not really maintaining it anymore.

AFAIK, PAM support would require additional fields (group ID, user ID and so on). Rather than adding custom purpose-specific fields for every request, I'm working on https://github.com/nitnelave/lldap/issues/67 that would allow...

I'll keep this issue open since we might want to have a nicer interface for it, such as finding a user ID that isn't taken yet and so on, but...

I guess it could make sense in the context of a migration to allow user creation to specify a UUID. Not for user modification though. I'd be open to a...

Oh, I think I know the problem here: `entryUUID` is not part of the default list of attributes returned for a user. Maybe that's what's missing?

LLDAP will return the UUID if it's requested in the request. By default the response contains all the fields, but for LLDAP there's a bug and the UUID is not...

Alright, as soon as the image builds (in a couple of minutes) you can try with the latest LLDAP, that should give you the entryUUID in the response.