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

Improve LDAP filter hint #2149

Open
dani-sanchez-dorado opened this issue Mar 4, 2025 · 1 comment
Open

Improve LDAP filter hint #2149

dani-sanchez-dorado opened this issue Mar 4, 2025 · 1 comment
Assignees

Comments

@dani-sanchez-dorado
Copy link
Collaborator

Hello,

I have wasted a lot of time testing the LDAP filter, because of the ambiguous text "Type a typical LDAP user name to fetch the attribute list". There is no explanation about the search parameters of this query. "Typical LDAP" is not a good hint.

Finally, I solve the mistery (with some help of Franky) !!! The search is done using the "cn" attribute. And this behavior can be changed using the "field" atribute in the settings file "ravada.conf". All this options are not clearly documented anywhere.!!

So, I propose: Change the "Type a typical LDAP user name to fetch the attribute list" message for something else most accurate. Something like "Query for LDAP cn attribute". Or you can add a hint (this "i" icon) explaining the query. A reference to the "field" attribute in the ravada.conf file would be great!

Thanks a lot!

@frankiejol frankiejol self-assigned this Mar 4, 2025
frankiejol added a commit that referenced this issue Mar 4, 2025
@frankiejol
Copy link
Member

Hello Dani. Thanks for your insights. It will help us improve the user interface.

We can't change the message to "Query for LDAP cn attribute" because that field name may change. Inserting the attribute name inside the text message would break the localization string. So what about keeping the text and adding an explanation ? It would appear on clicking the "i" icon as you suggested. I attach a screenshot. Also the "read more" link points to the document where you can read about the field configuration details.

Image

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

No branches or pull requests

2 participants