We are running into the same problem.
Please let us know when this is fixed :)
Kind regards,
Sander Botman
Schuberg Philis
Boeingavenue 271
1119 PD Schiphol-Rijk
http://www.schubergphilis.com
+31 207506848
+31 651425985
From: Joseph Smith [mailto:
Sent: woensdag 11 december 2013 0:20
To:
Subject: [chef] Re: Re: Re: Enterprise Chef: Chef Manager doesn't seem to use LDAP?
Hey folks,
I'm sorry for the delay in responding to you. We are currently working on the fix, and we'll get it out as soon as possible.
In the interim, I would advise that if you are using LDAP, do not upgrade to the new version of Chef Manager.
I will respond to this thread when there's a fix available.
Thanks for your patience - it's appreciated.
On Tue, Dec 10, 2013 at 3:12 PM, Christopher Armstrong <
" target="_blank">
> wrote:
Glad to hear it's not just us, Joshua. Nothing back from support yet, but they're definitely looking into it.
On Tue, Dec 10, 2013 at 3:08 PM, Joshua Buysse <
" target="_blank">
> wrote:
Chris -- did you hear anything back from support? I'm seeing the same thing.
We just upgraded to Enterprise Chef 11.0.2 and installed the Chef Manager and Reporting features as instructed
here and
here. After the upgrade, new employees who haven't used Chef before are unable to login - using the old webui, first login would prompt the user to connect or create a Chef account before logging them in. Now, it bounces them with no message. Tailing the
Chef server logs show that we're getting a 404 - user not found.
Is this known? Do we need to stick with the existing UI if we want to use LDAP in our organization?
--
Joshua Buysse, System Engineer
College of Liberal Arts, Office of Information Technology
University of Minnesota
"On two occasions I have been asked, 'Pray, Mr. Babbage, if you
put into the machine wrong figures, will the right answers come
out?' I am not able rightly to apprehend the kind of confusion of
ideas that could provoke such a question."
|