# Supermarket Authentication

**URL:** <https://discourse.chef.io/t/supermarket-authentication/5724>\
**Category:** Chef Infra (archive)\
**Created:** [September 2, 2014, 11:02pm UTC](https://discourse.chef.io/t/supermarket-authentication/5724 "2014-09-02T23:02:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Durfee\_Bernie\_GE\_Glo](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/durfee_bernie_ge_glo/32/97_2.png) [@Durfee\_Bernie\_GE\_Glo](https://discourse.chef.io/u/Durfee_Bernie_GE_Glo)\
**Post date:** [September 2, 2014, 11:02pm UTC](https://discourse.chef.io/t/supermarket-authentication/5724/1 "2014-09-02T23:02:19Z")

</div>

Are there hooks in place to make the authentication pluggable? What would it take to use another Authorization Server instead of oc-id?

---

<div class="post-metadata">

**Author:** ![Mark\_Mzyk\_OLD](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/mark_mzyk_old/32/197_2.png) [@Mark\_Mzyk\_OLD](https://discourse.chef.io/u/Mark_Mzyk_OLD)\
**Post date:** [September 3, 2014, 12:26am UTC](https://discourse.chef.io/t/supermarket-authentication/5724/2 "2014-09-03T00:26:10Z")

</div>

I have no idea, but Supermarket is entirely open sourced along with  
oc-id, so it should just be a matter of finding where authentication is  
done in Supermarket to answer that question.

Here are links to the repos:

> **[GitHub - chef/supermarket: Chef's community platform](https://github.com/chef/supermarket)**
>
> Chef's community platform. Contribute to chef/supermarket development by creating an account on GitHub.

> **[GitHub - chef-boneyard/oc-id: Chef Identity Service (\*DEPRECATED\*)](https://github.com/chef-boneyard/oc-id)**
>
> Chef Identity Service (\*DEPRECATED\*). Contribute to chef-boneyard/oc-id development by creating an account on GitHub.

- Mark

> Durfee, Bernie (GE Global Research) [mailto:bernie.durfee@ge.com](mailto:bernie.durfee@ge.com)  
> September 2, 2014 at 7:02 PM  
> Are there hooks in place to make the authentication pluggable? What  
> would it take to use another Authorization Server instead of oc-id?

---

<div class="post-metadata">

**Author:** ![coderanger](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/coderanger/32/5_2.png) [@coderanger](https://discourse.chef.io/u/coderanger)\
**Post date:** [September 3, 2014, 12:57am UTC](https://discourse.chef.io/t/supermarket-authentication/5724/3 "2014-09-03T00:57:37Z")

</div>

On Sep 2, 2014, at 4:02 PM, Durfee, Bernie (GE Global Research) [bernie.durfee@ge.com](mailto:bernie.durfee@ge.com) wrote:

> Are there hooks in place to make the authentication pluggable? What would it take to use another Authorization Server instead of oc-id?

It is just using OmniAuth ([https://github.com/opscode/supermarket/blob/master/config/initializers/omniauth.rb](https://github.com/opscode/supermarket/blob/master/config/initializers/omniauth.rb)) so anything that has an omniauth plugin will work (or you can write one).

--Noah

---

<div class="post-metadata">

**Author:** ![Christopher\_Webber](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/christopher_webber/32/250_2.png) [@Christopher\_Webber](https://discourse.chef.io/u/Christopher_Webber)\
**Post date:** [September 3, 2014, 11:42am UTC](https://discourse.chef.io/t/supermarket-authentication/5724/4 "2014-09-03T11:42:21Z")

</div>

So, in concept you could swap it out. The problem becomes that the API is authenticated using pem files. So either you will need to build something similar to oc-id to handle that, or you will want to use oc-id.

Thanks!

— cwebber

On Sep 2, 2014, at 4:02 PM, Durfee, Bernie (GE Global Research) [bernie.durfee@ge.com](mailto:bernie.durfee@ge.com) wrote:

> Are there hooks in place to make the authentication pluggable? What would it take to use another Authorization Server instead of oc-id?