How are you specifying the credentials? Are you sure the credentials being sent with the request are correct?
I just tested that I could create a .netrc file with the following content on a host other than pulp: machine pulp3-source-fedora30.localhost.example.com login admin password password and I was able to successfully execute from that same host: http http://pulp3-source-fedora30.localhost.example.com/pulp/api/v3/repositories/ On Wed, Oct 2, 2019 at 11:23 AM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > Updated /etc/pulp/settings.py to use ALLOWED_HOSTS = ['*'] and restarted > all services. Still getting 403 errors. > Also tried adding PULP_ALLOWED_HOSTS to > /etc/systemd/system/multi-user.target.wants/pulp-api.service and replacing > localhost with 0.0.0.0 as below > Environment=PULP_ALLOWED_HOSTS="['*']" > ExecStart=/usr/local/lib/pulp/bin/gunicorn pulpcore.app.wsgi:application \ > --bind '0.0.0.0:24817' \ > --access-logfile > > The problem persists. > > > From: [email protected] At: 10/02/19 10:37:17 > To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> > Cc: [email protected], [email protected] > Subject: Re: [Pulp-list] Access Pulp 3 Api from a remote machine > > > We do have ALLOWED_HOSTS = '*' in /etc/pulp/settings.py >> > > This variable must be a list, not sure if that is the problem. > > ALLOWED_HOSTS = ['*'] > > As environment variable it would be export PULP_ALLOWED_HOSTS="['*']" > > https://docs.djangoproject.com/en/2.2/ref/settings/#allowed-hosts > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
