Supermarket Authentication

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

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:

  • Mark

Durfee, Bernie (GE Global Research) 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?

On Sep 2, 2014, at 4:02 PM, Durfee, Bernie (GE Global Research) 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) so anything that has an omniauth plugin will work (or you can write one).

--Noah

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 wrote:

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