GetPersonaPhoto is broken, we get 401

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

We configured libravatar as described in the documentation for Microsoft Office 365, see https://docs.gitlab.com/ee/administration/libravatar.html#usage-examples-for-microsoft-office-365. We don't see any image.

Steps to reproduce

Example Project

What is the current bug behavior?

If I open the browser console, i can see 401 for the image urls. If open the image url in different tab, i can see the image. It looks like security boundaries.

What is the expected correct behavior?

I would expect to see the images.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Use the AzureAD Oauth user token to authenticate against the url.