Hi,
On 22. Sep 2017, at 17:17 , Stefan Seyfried
wrote: after the update to 2.8.3, I found that local users (most prominent the Admin user ;)) no longer work, when LDAP mode is enabled.
That's right. We've decided that in an OBS setup with LDAP enabled, the user management should only happen via the LDAP instance.
Well, that's nice that this was decided.
But that does throw away lots of useful usecases that -- even though the GUI elements were confusing before -- actually did work.
One example is again the Admin account ;-)
And service users for automated jobs, which often are hard to get into a corporate Directory.
So might I ask to reconsider this decision?
+1 Even worse: How can I do the initial bootstrapping of an obs system now? As of now I created the initial obs configuration using curl --insecure -0 --user 'Admin:<initialpw>' -X PUT -T /srv/obs/configuration-ox.xml https://buildservice.<domain>/configuration How can I do that now? Do we need to create an LDAP User with name Admin? -- kind regards, Carsten Hoeger Professional Services Email: carsten.hoeger@open-xchange.com ----------------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Directors: Frank Hoberg, Martin Kauss US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA ------------------------------------------------------------------------------------------