Bug 1298804 - Adding providers without first checking that credential were entered should not work.
Summary: Adding providers without first checking that credential were entered should n...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard: ui:provider:add
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-15 06:43 UTC by Mike Dahlgren
Modified: 2019-08-06 20:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 17:15:37 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Dahlgren 2016-01-15 06:43:17 UTC
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 20:01:07 UTC
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 17:15:37 UTC
Verified fixed in 5.7.0 beta1


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