mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 16:25:55 +03:00
[GH-ISSUE #1258] [FEATURE REQUEST] Template field, dropdown field and display field as QR #444
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#444
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sgofferj on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1258
Motivation
I am working with TAK servers whose user management is horrific. They do offer LDAP auth, though. They also offer a quick connect option with QR codes
Describe the solution you'd like
I would like to suggest 3 features:
1.) Template field
The field will accept a string. Certain codes are replaced by LDAP values, e.g. {user-cn}, {group-cn}, ... When made not-user-editable, the filed could e.g. a user-specific or group-specific link.
2.) Drop down field
The field is of type string but only options pre determined by the administrator can be chosen
3.) Display as QR
This would be a flag in the configuration which when set, will cause the field contents to be displayed as a QR code rather than as clear text. Together with the template field, this could provide quick link functionality e.g. for users of a mobile app which authenticates through LDAP.
Describe alternatives you've considered
One possible alternative would be to write a python script which does an LDAP search and creates templated links and QR codes to a PDF. There is no good alternative to Drop down fields. Manual input always carried the risk of errors.
@nitnelave commented on GitHub (Aug 22, 2025):
That's a bit too specific for my taste. I would consider that mostly out of scope for the project. However, with the upcoming plugin API, you'll be able to do the first one rather easily (you can overwrite the field value whenever an attribute changes).
The second one can also be kind of implemented: it's not as nice, but you can check that the value is one of the expected ones, and return the list of accepted values when there is an error.
As for the third one, that's out of scope. But it should be fairly simple to write a server that queries LLDAP and displays an attribute as QR code. I'm sure Claude or GPT can handle something like that.
@sgofferj commented on GitHub (Aug 22, 2025):
OK, thanks