summaryrefslogtreecommitdiffstats
path: root/keystone/clean.py
Commit message (Collapse)AuthorAgeFilesLines
* Clean hacking errors in advance of hacking updateMonty Taylor2013-08-151-4/+9
| | | | | | | | The next patch syncs with global requirements, including an update to hacking. These fixes align the codebase with those new rules. Change-Id: I16e5a4ffa877fb46d2fb28d881642185c801b628
* Increase length of username in DBAlvaro Lopez Garcia2013-08-151-3/+4
| | | | | | | | | Length of username in database may be too short for X.509 DNs and 255 seems a sane value for it. Fixes bug #1081932 Change-Id: Ie8f696845ea15d37cf13f3fe7978b22deac798b0
* Add checks to test if enabled is boolgalstrom212013-06-121-0/+4
| | | | | | fixes: bug #1167593 Change-Id: Ie18fa17f16383f31d8aa083e69fa501d80eb4553
* Http 400 when user enabled is not a booleanBruno Semperlotti2013-05-161-1/+11
| | | | | | | | | | | | | | | | | | | | | When creating or updating a user, no type check was performed on the enabled attribute. Therefore, if enabled value in JSON/XML is not a boolean buta string or an int, keystone responds with an incorrect Http 500 error code and the stacktrace. The change introduces a type validation of the enabled attribute at backend and api layer. If the type is not a boolean, keystone now returns an appropriate Http 400 error code with a message pointing a bad format for the attribute. Test cases have been added to file test_backend and test_content_types for testing the case when enabled attribute is a string or int when creating or updating user. The same correction can be done for create/update projects, domains. Change-Id: I7d2fe3acf0c4dbd3ce5bdf9f4d059df085853b84 Fixes: bug #1110435
* tenant to project in the apisAdam Young2013-01-281-2/+2
| | | | Change-Id: I1f6fdf304ca3ff0b6e0e05a71fd944189105c5b6
* Keystone server support for user groupsHenry Nash2013-01-081-0/+4
| | | | | | | | | | | | | | | | | | | | | | | This implements the server side of groups of users. This set of code provides all the crud functionality for groups as well as the corresponding support for role assignments. blueprint user-groups The following deficiencies existing with the current version and will be corrected ahead of the final Grizzly release: 1) There is only placeholder support for LDAP (Bug #1092187) 2) Domain role grants are accepted but not yet honored (Bug #1093248) 3) Token invalidation does not occur with group changes (Bug #1093493) This update also fills in missing v3 grant unit testing and v3 grant support within the kvs backend. In addition, there is a fix for Bug #1092200 (uncaught exception when listing grants) DocImpact Change-Id: Ibd1783b04b2d7804eff90312e5ef591dca4d0695
* Bug 1075090 -- Fixing log messages in python source code to support ↵Nachiappan VR N2012-12-041-6/+7
| | | | | | internationalization. Change-Id: I6b50abaa82effad8feaaac8d85086ca8b5d42590
* v3 IdentityDolph Mathews2012-11-201-7/+12
| | | | | | | - v3 identity tests (bug 1023930) - v3 identity implementation (bug 1023937) Change-Id: Ic46575afe9760d9da85e262d0cf063ea002d9dcd
* Added user name validation. Fixes bug 966251.Unmesh Gurjar2012-07-191-0/+7
| | | | | | | | 1. Verified name length while creating/updating user. 2. Disallowed blank user name in create/update. 3. Added unit test coverage. Change-Id: I55cd5daf34f4f57d4163be403a7a75c5d22baa62
* Added tenant name validation. Fixes bug 966249.Unmesh Gurjar2012-05-091-0/+44
1. Verified name length while creating/updating tenant (for all backends). 2. Disallowed blank tenant name in create/update. 3. Added unit test coverage. Change-Id: Ied1e2707ba16e14d791308fb618ca18effa0245f