Bug 1298804 - Adding providers without first checking that credential were entered should not work.
Adding providers without first checking that credential were entered should n...
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
All Linux
unspecified Severity low
: GA
: cfme-future
Assigned To: Dan Clarizio
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2016-01-15 01:43 EST by Mike Dahlgren
Modified: 2016-10-26 13:15 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-10-26 13:15:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Dahlgren 2016-01-15 01:43:17 EST
Description of problem:

When adding a provider such as VMWare or OpenShift, input validation should be performed to ensure that the provider can not be added without the user providing at least authentication credentials.

Version-Release number of selected component (if applicable):

How reproducible:
1. Go to the containers tab -> Click Providers
2. Click on Configuration -> Add new provider
3. Fill out all fields correctly except for Credentials -> Token
4. Click "Add" at the bottom right

Actual results:
Provider will add successfully but be inoperable.

Expected results:
The UI would prompt the user to enter credentials (in this case a token)

Additional info:
Comment 2 Greg Blomquist 2016-01-15 15:01:07 EST
John, it was my understanding that at some point way in the past (pre-acquisition) the "Add new provider" page was made this way intentionally.  I.e., credentials were not required when adding a provider.

I don't know the back story.  Can you add your perspective here?
Comment 4 Mike Dahlgren 2016-10-26 13:15:37 EDT
Verified fixed in 5.7.0 beta1

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