Bug 1377659 - Token field gets pre-populated with the token that was used with the last provider
Summary: Token field gets pre-populated with the token that was used with the last pro...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Aparna Karve
QA Contact: Einat Pacifici
URL:
Whiteboard: browser:provider
: 1422954 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 10:25 UTC by Tony
Modified: 2018-10-02 14:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
token field is pre-populated (71.78 KB, image/png)
2016-09-20 10:25 UTC, Tony
no flags Details
evm.log (251.14 KB, text/plain)
2016-09-20 10:28 UTC, Tony
no flags Details
production.log (61.67 KB, text/plain)
2016-09-20 10:29 UTC, Tony
no flags Details
audit.log (949 bytes, text/plain)
2016-09-20 10:30 UTC, Tony
no flags Details

Description Tony 2016-09-20 10:25:38 UTC
Created attachment 1202813 [details]
token field is pre-populated

CFME 5.7.0.0

Openshift 3.2

Description of problem:

When adding back the provider that was attached to CFME before and then deleted, the first token field gets automatically populated. The issue can also be replicated when attaching a brand new provider - the token field gets populated with the token that was used last. 


Steps to Reproduce:

1.Attach a new provider to CFME

2.Verify that provider was successfully added to CFME

3.Delete the provider

4.Try adding the same provider to CFME

5.Alternately, after deleting the provider, attach a brand new provider to CFME


Actual results:

The firs token field is automatically pre-populated



Expected results:

When adding the provider, the token should be filled in twice

Comment 2 Tony 2016-09-20 10:28:13 UTC
Created attachment 1202817 [details]
evm.log

Comment 3 Tony 2016-09-20 10:29:18 UTC
Created attachment 1202818 [details]
production.log

Comment 4 Tony 2016-09-20 10:30:18 UTC
Created attachment 1202819 [details]
audit.log

Comment 9 Tony 2016-12-19 09:25:34 UTC
The issue is relevant for Firefox

Comment 10 Federico Simoncelli 2017-02-20 10:20:14 UTC
*** Bug 1422954 has been marked as a duplicate of this bug. ***

Comment 15 Josh Carter 2018-10-02 14:31:54 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 16 Josh Carter 2018-10-02 14:34:16 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


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