| Summary: | Infoblox authentication errors do not propagate into WebUI/CLI/API | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Renzo Nuccitelli <rnuccite> | ||||||||
| Component: | DHCP & DNS | Assignee: | Lukas Zapletal <lzap> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.3.0 | CC: | bkearney, dmitri, jcallaha | ||||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||||
| Target Release: | Unused | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-08-02 20:57:28 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1402685 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Renzo Nuccitelli
2016-12-06 16:30:55 UTC
Created attachment 1228624 [details]
save error msg
Created attachment 1228625 [details]
delete error msg
If password is changed back to original value used on installer, delete and creation work as expected. Thanks that's enough. It looks like the plugin uses two gems: https://github.com/govdelivery/infoblox https://github.com/lostisland/faraday There is zero error handling, we need to catch the exception in the plugin Proxy's dhcp module returns all errors raised by a provider, including Infoblox' 401 errors. Dhcp module rewrites errors, however: 401 returned by Infoblox is recast by the proxy to a generic 400 error. It would probably be easier to handle these exceptions in foreman if they were more specific (as it wouldn't require parsing of error messages). It looks like foreman's error message processing might have something to do with this too -- delete record error message above is a generic one, while a quick look at the source suggests that it should contain error text returned by the proxy. Here's the error I'm getting when infoblox authorization fails (it's content-type of text/html): Error: 401 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> D, [2016-12-21T13:36:36.469288 ] DEBUG -- : Error: 401 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> (Infoblox::Error) Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. |