No description
It appears the recent migration of the LDAP code and add of a check for the admin username/password being invalid *broke the LDAP password check*, allowing any password to succeed for login. This fixes the problem, add unit tests to verify the fix and add some tests to our other external auth test suite. A release will be needed immediately along with an announcement |
||
---|---|---|
auth | ||
avatars | ||
binary_dependencies | ||
buildman | ||
buildstatus | ||
conf | ||
contrib/osx | ||
data | ||
digest | ||
emails | ||
endpoints | ||
events | ||
features | ||
formats | ||
grunt | ||
health | ||
screenshots | ||
static | ||
storage | ||
templates | ||
test | ||
tools | ||
util | ||
workers | ||
.dockerignore | ||
.gitignore | ||
alembic.ini | ||
app.py | ||
application.py | ||
Bobfile | ||
build.sh | ||
CHANGELOG.md | ||
config.py | ||
dev.df | ||
Dockerfile | ||
external_libraries.py | ||
initdb.py | ||
local-docker.sh | ||
local-run.sh | ||
local-test.sh | ||
MAINTAINERS | ||
pylintrc | ||
README.md | ||
registry.py | ||
requirements-dev.txt | ||
requirements-nover.txt | ||
requirements.txt | ||
ROADMAP.md | ||
verbs.py | ||
web.py |
Quay.io - container image registry
Quay.io is a container image registry with managements APIs, a Docker registry API, a container build system. The application is implemented as a set of API endpoints written in python and an Angular.js frontend.
Setup Development Environment
If you are doing local development on your workstation against the code base follow these instructions.
OS X
git clone git@github.com:coreos-inc/quay.git
cd quay
./contrib/osx/local-setup.sh
Running Development Environment
Now run the server; it will use sqlite as the SQL server.
./local-run.sh
Now quay will be running on: http://127.0.0.1:5000
The username is devtable
and the password is password
.