Problem with clients authentication to the server


Chronological Thread 
  • From: Albert Llop <mrsimo@gmail.com>
  • To: chef@lists.opscode.com
  • Subject: Problem with clients authentication to the server
  • Date: Thu, 28 May 2009 09:27:12 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=sI5ihG6mP5VlxgLFN9tMeYxoGdGXtHtU4hU0w/Zake0UHzHWBpTxMAhKWtCcq3pa05 KoNn11bPovQCxR9EAmxMlwb8J6ZwWgn2xrtEUgzMQBRrpKVcJ3/MnsrvzAqaaXhZXC2g ZbyTN5eptGiLAWBsG/m5Ck2ogS6I5RXsOfmU8=

Hi there,

we've been trying to get Chef on and going in my Company since Joshua Sierles' presentation at EuRuKo this month, and we've encountered a brick wall which I'd like to share with you and see if anyone can help.

The problem is explained in this gist http://gist.github.com/118534

I've been trying all this in amazon ec2 small instances with a 9.04 ubuntu from alestic. I've managed to get the server and a client working, installing everything with chef-solo (except for couchdb in the server, but that's fixed installig the package manually). The client appears in the registrations section of the admin, and I validate it successfully, both manually and automatically with the validation_token config attribute.

After that I cannot see any nodes on the rest of the sections. The client gives the error you can see on the gist, and the server's merb log is there aswell. That line seems to be where openid is trying to authenticate the client (line 44 of openid_consumer.rb)

I've trying plenty of things and none has worked so far.

Any help would be most welcome, since I'm starting to understand how the whole chef thing works, but things like these scare the hell out of us.

Thanks a lot!

--
Albert Llop


  • Problem with clients authentication to the server, Albert Llop, 05/28/2009

Archive powered by MHonArc 2.6.16.

§