Bug 1356302

Summary:	EMS Form cannot create new ems container provider with bearer (default) authentication
Product:	Red Hat CloudForms Management Engine	Reporter:	Aparna Karve <akarve>
Component:	UI - OPS	Assignee:	Aparna Karve <akarve>
Status:	CLOSED ERRATA	QA Contact:	Einat Pacifici <epacific>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.6.0	CC:	akarve, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.0	Flags:	epacific: automate_bug+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.7.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1372762 (view as bug list)		Environment:
Last Closed:	2017-01-04 12:57:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Container Management	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1372762

Description Aparna Karve 2016-07-13 22:50:29 UTC

Description of problem:EMS Form cannot create new ems container provider with bearer (default) authentication


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


How reproducible:


Steps to Reproduce:
1. Add a new Container Provider
2. Enter the credentials and hit Validate
3.

Actual results:
"Credential Validation was not successful, missing credentials" message shows up

Expected results:
For correct credentials, validation should go through successfully


Additional info:

Comment 2 Satoe Imaishi 2016-08-18 19:40:30 UTC

Aparna, can you add PR link that fixed this issue?

Comment 3 Aparna Karve 2016-08-18 20:19:30 UTC

Satoe, here you go -

https://github.com/ManageIQ/manageiq/pull/9775

Comment 6 Dafna Ron 2016-11-14 11:02:08 UTC

seems like an old bug since we are able to add container providers and validate. 
moving to verified for 5.7

Comment 8 errata-xmlrpc 2017-01-04 12:57:33 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0012.html