{"push_id":537317646,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"59e2d4034c352d39c5dedf5ff724e14e4c51a94b","before":"16acdf713926ddf4bd96667c5bd0f0d7400ef6f3","commits":[{"sha":"4748211adbc6121701239cd88ae7b1a121156824","author":{"email":"ff525e42d91daf173fc2743f7e29684516dae756@redhat.com","name":"Bronagh Sorota"},"message":"Go with the exception's own 'message' in the verify_credentials method.\n\n A 401 exception can be returned by the WinRM service on the SCVMM box for reasons other than a user has entered invalid credentials. For example, if we set the winrm/config/service/AllowUnencrypted value to 'false' we get the same 401 error, probably because it is still a denial of access..\nI think it is safer just to stick with the message built into the exception. That said, I am open to appending some clues to the message such as \"Check credentials and WinRM configuration settings\"… or something like that.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1131236","distinct":true,"url":"https://api.github.com/repos/ManageIQ/manageiq/commits/4748211adbc6121701239cd88ae7b1a121156824"},{"sha":"59e2d4034c352d39c5dedf5ff724e14e4c51a94b","author":{"email":"4404c26c82eea684eb4004177464b4faaf5500a0@gmail.com","name":"Jason Frey"},"message":"Merge pull request #1269 from bronaghs/scvmm_misleading_auth_error\n\nSCVMM - Printing the exception's own message in verify_credentials","distinct":true,"url":"https://api.github.com/repos/ManageIQ/manageiq/commits/59e2d4034c352d39c5dedf5ff724e14e4c51a94b"}]}