Bug 47711 - Consider shipping Jenkins app with LDAP auth already configured
Consider shipping Jenkins app with LDAP auth already configured
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.3
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-09-03 14:49 CEST by Valentin Heidelberger
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Heidelberger univentionstaff 2018-09-03 14:49:16 CEST
Jenkins currently ships without a ready-to-go LDAP auth configuration. One has to manually enable and configure LDAP auth via Settings -> Global Security at the moment.

I think users might expect the app to ship with such a configuration (at least I did), because it's in the public App Center.
On the other hand Jenkins itself does not ship ready-to-go either. There's still an installation wizard to be completed. The wizard also contains a plugin selection where a user could decide to not install the required LDAP plugin (which is marked as suggested and thus installed by default) at all.
I think it would be nice to have a working LDAP auth, if the user decides to keep the LDAP plugin in the installation wizard. It might also be a good idea to activate LDAP as auth backend by default (maybe just granting Domain Admins access?)
Not sure how all that could be achieved from a technical perspective though.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:43:11 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.