This was fixed in a prior release of Pulp, but we never put it through the QE process. Moving to ON_QA.
verified [root@ibm-x3550m3-08 ~]# rpm -qa pulp-server pulp-server-2.4.0-0.19.beta.el6.noarch [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl -d '{}' https://localhost/pulp/api/v2/repositories/zoo/actions/resolve_dependencies/ -k {"http_request_method": "POST", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/repositories/zoo/actions/resolve_dependencies/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl https://localhost/pulp/api/v2/consumer_groups/test-group/bindings/ -k {"http_request_method": "GET", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/consumer_groups/test-group/bindings/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl https://localhost/pulp/api/v2/repo_groups/search/ -k {"http_request_method": "GET", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/repo_groups/search/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl -d '{}' https://localhost/pulp/api/v2/repo_groups/search/ -k {"http_request_method": "POST", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/repo_groups/search/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl -d '{}' https://localhost/pulp/api/v2/repo_groups/test-id/actions/publish/ -k {"http_request_method": "POST", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/repo_groups/test-id/actions/publish/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]# [root@ibm-x3550m3-08 ~]# curl https://localhost/pulp/api/v2/users/search/ -k {"http_request_method": "GET", "exception": null, "error_message": "Pulp exception occurred: AuthenticationFailed", "_href": "/pulp/api/v2/users/search/", "http_status": 401, "error": {"code": "PLP0000", "data": {}, "description": "Pulp exception occurred: AuthenticationFailed", "sub_errors": []}, "traceback": null, "auth_error_code": "invalid_ssl_certificate"}[root@ibm-x3550m3-08 ~]#
This has been fixed in Pulp 2.4.0-1.