Honor schema validation everywhere
schema validation was enforced by jsonschema for most of the V3 API, but we also need enforce the schema validation for the legacy keystone extensions after those extensions were moved into cores and enabled by default.
It's also great if we can enable the same thing for V2 APIs since V2 APIs will hang around for a long time and we not sure if there is a time that we will drop V2 support, and V2 API is still used extensively.
It makes for a more robust user experience if we get all of those done.
Some components we need to consider includes:
- endpoint_policy
- federation
- endpoint_filter
etc.
and all the V2 API stuff?
Blueprint information
- Status:
- Complete
- Approver:
- Steve Martinelli
- Priority:
- Medium
- Drafter:
- Dave Chen
- Direction:
- Approved
- Assignee:
- Dave Chen
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-3
- Started by
- Dave Chen
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
(stevemar) bumping to newton-2
(stevemar 7/11/16) bumping to newton-3
(gagehugo - V3 appears to be done according to stevemar/DaveChen: https:/
as discussed in the keystone meeting, this blueprint should focus on providing schema validation for v3 extensions, then if possible, v2 calls as well.
Gerrit topic: https:/
Addressed by: https:/
Add schema for identity provider
Addressed by: https:/
Remove redundant check after enforcing schema validation
Addressed by: https:/
Add schema for federation protocol
Addressed by: https:/
Add schema for OAuth1 consumer API
Addressed by: https:/
Add schema for enabling a user
Addressed by: https:/
Add schema validation to create role
Addressed by: https:/
Add schema validation to v2 create tenant
Addressed by: https:/
Add schema validation to create service in v2
Addressed by: https:/
Add the missing testcases for `name` and `enabled`
Addressed by: https:/
No need the redundant validation in manager level
Addressed by: https:/
Add schema validation to create user v2
Addressed by: https:/
Add schema validation to update user in v2
Addressed by: https:/
Add schema validation to v2 update tenant
