Bug 1563540
| Summary: | [Ansible Tower] - unexpected token - credentials validation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Pavol Kotvan <pakotvan> | ||||
| Component: | Providers | Assignee: | Alexander Zagaynov <azagayno> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nandini Chandra <nachandr> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.9.0 | CC: | bsorota, cpelland, dberger, gblomqui, jfrey, jhardy, obarenbo | ||||
| Target Milestone: | GA | ||||||
| Target Release: | cfme-future | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | tower | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1614417 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-06-11 15:26:44 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | Bug | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | Ansible | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1614417 | ||||||
| Attachments: |
|
||||||
|
Comment 4
bascar
2018-04-10 12:47:14 UTC
Created attachment 1458325 [details]
3.2.2 different message
I'm getting much cleaner message when using Tower 3.2.2 (see attachment 1458325 [details]).
However I'm not sure, if we should be assuming why the credential validation failed. It should be the Tower telling us the cause. If Tower API doesn't state that clearly, why should CFME be the one guessing what the problem is? What do you think, Brad?
I agree that it would make sense to have the "ENABLE HTTP BASIC AUTH in Tower has to be ON" in our documentation, though.
We should show the message as the user trying to add this is an advanced admin type user. Just show the message without interpretation. If this in fact the message being sent by Tower and it is incorrect then we should place a BZ on Tower. Even with all of that, this is something that needs to go on the documentation and even explained on the screen above the validate button like: Please note that in Tower you must set a configuration setting: "Enable HTTP BASIC Auth" as described in the product documentation. Ok. Will do. I'll place the note on the provider config screen and clone this BZ against documentation team. ;) |