Commit Graph

11 Commits

Author SHA1 Message Date
Kristi Nikolla 8153a9d592 Add expiring user group memberships on mapped authentication
When a federated user authenticates, they are added to their
mapped groups during shadowing.

Closes-Bug: 1809116

Change-Id: I19dc400b2a7aa46709b242cdeef82beaca975ff3
2020-04-07 19:30:57 -04:00
Vishakha Agarwal 4530041931 Remove six usage
This repo does not support Python 2 anymore, so we don't need
six for compatibility between Python2 and 3, convert six usage to Python
3 code.

Change-Id: Icba56808f38277b27af2ae5aac4b8507dee71b3b
2020-01-30 06:06:51 +00:00
Colleen Murphy 131f7ddd4e Update API version for access rules
This change updates the minor API version for the new access rules
feature for application credentials, and also adds documentation for
the new feature to the API reference as well as a release note.

bp whitelist-extension-for-app-creds

Change-Id: I8a03223df63877a4f86fbe7e9fa382fdd96c5934
2019-09-14 03:14:45 -07:00
Adrian Turjak a011fb6789 bump Keystone version for Stein
Change-Id: I2c3aa095f0ceb28a97a61db27e595bc504b75bd0
2019-01-22 15:34:06 +13:00
Zuul a633001b20 Merge "Provide a Location on HTTP 300" 2018-11-09 23:20:30 +00:00
Gage Hugo 7eec2c5de0 Remove check for disabled v3
We should never be disabling an API version now, this change
removes a check for seeing if v3 is disabled. Since we should not
be disabling an API version anymore, this check is not needed.

Also removed one test for checking if an API version is disabled.

Change-Id: I08404bf82f26173c68397e33f9e43fadf34ea15e
2018-10-30 12:51:16 -05:00
Morgan Fainberg 50e3fe5c94 Provide a Location on HTTP 300
To best adhere to the RFC2616, we should emit a Location header when
issuing an HTTP 300 to point to the preferred version. While we only
have a single version active it is 'v3'. In the future it should
always be the most recent set of CRUD. This location is strictly for
CRUD purposes and will lean on the WWW-Authentication URI to point
to the most correct AUTH uri.

Change-Id: Ibdd53f236a3c51d1aa23eac35dd595e2dae79ba6
closes-bug: #1230927
2018-10-26 09:19:57 -07:00
Zuul 2af3707ace Merge "Remove pre-flask legacy code" 2018-10-24 08:29:20 +00:00
Colleen Murphy 0bac1d7e8a Update API version to 3.11
Co-authored-by: Lance Bragstad <lbragstad@gmail.com>

Change-Id: I62b8e05b3e347724218d044dfe73640fff9cc78c
2018-10-16 16:32:29 +02:00
Morgan Fainberg 184c84ae76 Remove pre-flask legacy code
This removes common.controller, common.extension, common.router, and
common.wsgi. Relevant code from common.wsgi (used by AuthContext) was
moved into keystone.server.flask.request_processing.middleware.auth_context.

keystone.api.discovery now uses keystone.flask.base_url

test_middleware and test_exception were modified to reflect the changes
to the remaining code from keystone.common.wsgi

keystone.common.authorization only holds a couple constants for auth
work now.

Routes is removed from requirements.txt

Release-Note for migration to flask added.

Change-Id: I81563b6a49c8f12ecade058a9483f3b6f070dc72
Closes-Bug: #1776504
2018-10-15 10:56:26 -07:00
Morgan Fainberg 3e3ba18bfa Convert json_home and version discovery to Flask
Move the JSON Home Document and Version Discovery Documents out of
the webob-based mapper and into Flask.

This change removes the keystone.version.controller and
keystone.version.router modules as they have been moved into
keystone.api.discovery.

The keystone.api.discovery module is somewhat specialized as there
are no "resources" and it must handle multiple types of responses
based upon the ACCEPTS header (JSON Home or JSON). In lieu of the
flask-RESTful mechanisms, keystone.api.discovery utilizes bare
flask blueprint and functions. Minor scaffolding work has been done
to ensure the discovery blueprint can be loaded via the loader loop
in keystone.server.flask.application (a stub object in
keystone.api.discovery).

Partial-Bug: #1776504
Change-Id: Ib25380cefdbb7147661bb9853de7872a837322e0
2018-06-27 09:58:35 -07:00