Testcases for Folsom: Access Key Authentication (blueprint)

Bug #1005968 reported by Ravikumar Venkatesan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Invalid
Wishlist
Ravikumar Venkatesan

Bug Description

The following test cases have to be written to support the blueprint - Access Key Authentication (blueprint)https://blueprints.launchpad.net/keystone/+spec/access-key-authentication

Existing Service tests:
-----------------------
1. All Nova tests to run using accesskey/secret key.new variables to be added to tempest.conf, and switch to use accesskey/secret key . Nosetest to be run using the switch .
2. All Swift tests to run using accesskey/secret key

New Tests:
---------
1) Create key - PUT /v2.0/accessKeys
2) List key - GET /v2.0/accessKeys
3) Update keys - PUT /v2.0/accessKeys/{accessKeyID}
4) Delete key - DELETE /v2.0/accessKeys/{accessKeyId}

description: updated
description: updated
Revision history for this message
David Kranz (david-kranz) wrote :

This blueprint is not targeted to Folsom. This ticket should be updated when/if the blueprint is targeted for a release.

Changed in tempest:
status: New → Incomplete
importance: Undecided → Wishlist
Revision history for this message
Ravikumar Venkatesan (ravikumar-venkatesan) wrote :

we will keep this open . Will pick up this when blueprint is implemented,

Changed in tempest:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.