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

Add EVENTs to get additionals user attributes from LDAP and show them #1660

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

maturbet
Copy link
Contributor

No description provided.

@maturbet
Copy link
Contributor Author

Plugin exemple for use : https://github.com/Association-Cocktail/LdapCacheFields

@maturbet
Copy link
Contributor Author

@vboctor
Is it what you expect here ? #1637 (comment)

@dregad dregad force-pushed the maturbet-ldapfieldsevent-1 branch from 191a3a2 to 5aa5040 Compare June 4, 2020 16:21
@vboctor vboctor added the plugins Pull requests related to plugins and events label Apr 9, 2023
@maturbet maturbet force-pushed the maturbet-ldapfieldsevent-1 branch from c8a68ff to 298787a Compare July 6, 2023 08:31
@maturbet maturbet force-pushed the maturbet-ldapfieldsevent-1 branch 2 times, most recently from c2b75b1 to 6328e50 Compare October 16, 2023 07:44
Copy link
Member

@vboctor vboctor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. For attributes to display the plugin event should return logical data that is rendered by core. We have been moving away from have events echo html output. Reason is that it is not API friendly and breaks whenever Mantis UI is changed.

  2. For the extra LDAP fields, why not just use a config option rather than a plugin event?

  3. Should the extra LDAP info be included in the REST API that retrieves user info? eg in ldap_fields element?

@maturbet
Copy link
Contributor Author

  1. For attributes to display the plugin event should return logical data that is rendered by core. We have been moving away from have events echo html output. Reason is that it is not API friendly and breaks whenever Mantis UI is changed.

I think I can make that change.

  1. For the extra LDAP fields, why not just use a config option rather than a plugin event?

I used a plugin event following a past suggestion but I'll use the method you prefer ...

  1. Should the extra LDAP info be included in the REST API that retrieves user info? eg in ldap_fields element?

Probably, it makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugins Pull requests related to plugins and events
Projects
None yet
2 participants