Chef Server 12.4.0 and 12.4.1 have been released

Hello Chefs,

We have recently released both Chef Server 12.4.0 and 12.4.1.

Chef Server 12.4.0 includes numerous Ruby on Rails CVE fixes that were announced last week and some new features. For a full description see our blog post:

Chef Server 12.4.1 is a patch to fix a bug in Chef Server 12.4.0 that would prevent upgrades from Chef Server 11. See the full blog post here:

Thanks for using Chef!

  • David McCown
    Chef Software Engineer

An automatic /universe is a seriously useful addition. Is that
automatically added per org?

Yes, it’s there for everyone. However, both berkshelf and policyfiles will need work to support it, and that’s not happened yet (I don’t know anything about librarian, but if it uses /universe on supermarket it too will need work).


So, I upgraded one of our chef servers the other day. I try to curl the \universe endpoint thusly:
curl https://myawesomechefserver.local/organizations/myawesomeorg/universe

but all I get is this:

<html><body>You are being <a href="https://myawesomechefserver.local/login">redirected</a>.</body></html>

I do have the chef-manage stuff installed there. Does the \universe endpoint work with the web ui installed?

yes, but it’s an endpoint that needs authentication (and also needs content type to be set to application/json). You can use knife raw /universe to see the output.

Is there a way to disable authentication on /universe so that existing tools work? I think that’d be a useful toggle; it’s unclear when Berkshelf et al will support the authenticated endpoint.


No, the new endpoint is understood to be unusuable at this time. It's just being put in place for future development.

It’s not actually the authentication that prevents it being immediately useful.

Supermarket will send back a tarball of the cookbook, whilst the chef server will give a list of files that you then download. So we have to fix berks or policyfile regardless.