Hide Forgot
Created attachment 1143406 [details] Error screenshot Description of problem: While attempting to log in via the RH Access module, I am told that the login failed. The Chrome console then shows a 500 error after the request. Version-Release number of selected component (if applicable): Satellite 6.1 Beta Snap 6 Compose 1 How reproducible: Always Steps to Reproduce: 1. Attempt to log in to Red Hat Access via the UI module with the same name. 2. View results. Actual results: Login failed with proper credentials. 500 error seen in web console. Expected results: Login succeeds with proper credentials. No errors seen.
@jcallaha, Can you provide the server side logs (/var/log/foreman/production.log?) with the exception trace? Thanks!
Created attachment 1143902 [details] production.log
Bug is caused by changes to http proxy settings handling in 6.2. I will impact both the Insights and Red Hat Access search/case management when an http proxy is configured for the Satellite server.
Builds available at: http://download.eng.bos.redhat.com/brewroot/packages/tfm-rubygem-foreman-redhat_access/1.0.3/1.el6sat/noarch/tfm-rubygem-foreman-redhat_access-1.0.3-1.el6sat.noarch.rpm http://download.eng.bos.redhat.com/brewroot/packages/tfm-rubygem-foreman-redhat_access/1.0.3/1.el7sat/noarch/tfm-rubygem-foreman-redhat_access-1.0.3-1.el7sat.noarch.rpm
Verified in Satellite 6.2 Beta Snap 8 compose 1. The module now works as expected.
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://access.redhat.com/errata/RHBA-2016:1501