Need Configuration Setting For REST API per Branded SSO Site
Bug #537657 reported by
Danny Tamez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical SSO provider |
Fix Released
|
Medium
|
Szilveszter Farkas | ||
Bug Description
Currently we have two wsgi files in config-staging and config-production named django.wsgi and django-api.wsgi By switching the contents of the files we can enable or disable the REST api for a site.
We need to have just one file and introduce a setting that we can use to enable or disable the api without making a code/file change. This setting can't be in settings.py since the wsgi file is executed before django can read the settings file.
Revision history for this message
| Szilveszter Farkas (phanatic) wrote | #1 |
| Changed in canonical-identity-provider: | |
| assignee: | nobody → Szilveszter Farkas (phanatic) |
| status: | New → In Progress |
| Changed in canonical-identity-provider: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Julien Funk (jaboing) wrote | #2 |
| Changed in canonical-isd-qa: | |
| assignee: | nobody → Julien Funk (jaboing) |
| Changed in canonical-isd-qa: | |
| status: | New → Invalid |
| Changed in canonical-identity-provider: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
According to my tests on EC2 it's possible to have a variable defined in settings.py based on which one can disable the API for that given deployment in the WSGI file.
I'll propose a merge request for this, just to make sure it goes through peer review.