Feature #3632
Cover astakos API on clients and create the corresponding user.* commands
Status: | Closed | Start date: | 04/19/2013 | |
---|---|---|---|---|
Priority: | Medium | Due date: | 04/26/2013 | |
Assignee: | Stavros Sachtouris | % Done: | 100% |
|
Category: | kamaki | Spent time: | 8.00 hours | |
Target version: | v0.10 |
Related issues
Associated revisions
Parse publicURL to fix astakos init, pretty quotas
Refs: #3632
Implement a user_list to list cached shell users
Refs: #3632
Implement user_info to show current user info
Refs: #3632
Implement user_get/set for session user
Refs: #3632
user_info --> user_get
Each kamaki session has a session user
The user defined in the config file through cloud....token
During the session, kamaki users may authenticate more users by tokens
and switch between them with user_set command
When authenticating a user, kamaki asks if you need to store this users
token as the session token
Allow multiple tokens per cloud configuration
Refs: #3632
Add name and uuid of session user to shell greet
Refs: 3632
History
#1 Updated by Stavros Sachtouris about 10 years ago
- Target version deleted (
v0.9)
#2 Updated by Stavros Sachtouris about 10 years ago
- Target version set to v0.10
#3 Updated by Stavros Sachtouris almost 10 years ago
- % Done changed from 0 to 50
kamaki user commands are used to store user authentication info (endpoints, etc.) and switch between users
#4 Updated by Stavros Sachtouris almost 10 years ago
- % Done changed from 50 to 60
Allow multiple tokens per cloud configuration
[cloud "mycloud"]
url = ...
token = u53r70o3n1== u53r70o3n2== u53r70o3n3==
#5 Updated by Stavros Sachtouris almost 10 years ago
- Status changed from New to Resolved
- % Done changed from 60 to 100
#6 Updated by Stavros Sachtouris almost 10 years ago
- Status changed from Resolved to Closed