Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1576601 - [RFE] Set ttl auth token for API for specific users
Summary: [RFE] Set ttl auth token for API for specific users
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Martin Kourim
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-09 22:39 UTC by David Luong
Modified: 2018-12-17 20:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-17 20:34:42 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)

Description David Luong 2018-05-09 22:39:16 UTC
1. Proposed title of this feature request
Set ttl auth token for API for specific users

3. What is the nature and description of the request?
Change API ttl token time for individual users

5. How would the customer like to achieve this? (List the functional requirements here)

Either through advanced config where the api ttl token is or through where we control RBAC

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Test to see if a specific user's token is still valid as opposed to all other users

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages or components.

Comment 6 Joe Vlcek 2018-12-17 20:34:42 UTC
I'm closing this PR. The associated case is CLOSED.

Please reopen this PR with more information if this is still an issues.


Note You need to log in before you can comment on or make changes to this bug.