Merge branch 'docker-registry' into 'master'
Added authentication service for docker registry This adds a simple authentication service for docker which uses current user credentials to authenticate pulls and pushes. I have only one concern. Since the `.docker/config` is unencrypted, thus the password for user stored there is unencrypted, maybe we should from the start implement function to generate/provide a separate password just for the purposes of accessing docker registry? What do you think @jacobvosmaer @sytses @marin? cc @marin See merge request !3787
Showing
... | @@ -36,6 +36,7 @@ gem 'omniauth-shibboleth', '~> 1.2.0' | ... | @@ -36,6 +36,7 @@ gem 'omniauth-shibboleth', '~> 1.2.0' |
gem 'omniauth-twitter', '~> 1.2.0' | gem 'omniauth-twitter', '~> 1.2.0' | ||
gem 'omniauth_crowd', '~> 2.2.0' | gem 'omniauth_crowd', '~> 2.2.0' | ||
gem 'rack-oauth2', '~> 1.2.1' | gem 'rack-oauth2', '~> 1.2.1' | ||
gem 'jwt' | |||
# Spam and anti-bot protection | # Spam and anti-bot protection | ||
gem 'recaptcha', require: 'recaptcha/rails' | gem 'recaptcha', require: 'recaptcha/rails' | ||
... | @@ -224,6 +225,7 @@ gem 'request_store', '~> 1.3.0' | ... | @@ -224,6 +225,7 @@ gem 'request_store', '~> 1.3.0' |
gem 'select2-rails', '~> 3.5.9' | gem 'select2-rails', '~> 3.5.9' | ||
gem 'virtus', '~> 1.0.1' | gem 'virtus', '~> 1.0.1' | ||
gem 'net-ssh', '~> 3.0.1' | gem 'net-ssh', '~> 3.0.1' | ||
gem 'base32', '~> 0.3.0' | |||
# Sentry integration | # Sentry integration | ||
gem 'sentry-raven', '~> 0.15' | gem 'sentry-raven', '~> 0.15' | ||
... | ... |
lib/json_web_token/token.rb
0 → 100644
Please register or sign in to comment