feat: map profile image URL to authenticatedUser.avatar on hydration

[SantiagoSuHe]

Summary

When hydrateAuthenticatedUser() calls the accounts API, the response includes profile_image.image_url_full — either the user's uploaded photo or a backend-generated initials avatar. This URL was never mapped to authenticatedUser.avatar, so every MFE header was ignoring it and falling back to a generic icon.

This PR fixes that with a single change in AxiosJwtAuthService.hydrateAuthenticatedUser():

avatar: userData.profileImage?.imageUrlFull || null,

authenticatedUser.avatar is now populated for any MFE that calls initialize() with hydrateAuthenticatedUser: true, without requiring changes in individual MFEs.

Context

This is part of a broader effort to replace the generic grey silhouette placeholder with a personalized initials avatar (a colored circle with the user's initials, similar to Google and Slack). The backend change that generates the initials image is in a companion PR:

• Backend (openedx-platform): feat: generate initials avatar as default profile image openedx-platform#38638 — generates a JPEG initials avatar on the server when the user has no uploaded photo. The image URL is returned in profile_image.image_url_full from the accounts API.
• Profile MFE: fix: show backend-generated avatar when no photo has been uploaded frontend-app-profile#1351 — fixes the profile page body, which was checking has_image and ignoring any available URL.

This frontend-platform change is the piece that connects the backend output to every MFE header at once.

How it works end to end

1. User logs in — backend generates initials avatar JPEG (if no uploaded photo)
2. MFE initializes with hydrateAuthenticatedUser: true
3. frontend-platform calls /api/user/v1/accounts/:username
4. profile_image.image_url_full → authenticatedUser.avatar  ← this PR
5. MFE header reads authenticatedUser.avatar and shows the image

Without this change, step 4 never happens and the header shows the generic icon regardless of what the backend returns.

Changes

• src/auth/AxiosJwtAuthService.js — 6 lines added, 1 changed. No new dependencies, no API changes, no breaking changes.

Test plan

• Start a local Open edX instance with the companion backend PR applied
• Log in as a user with no uploaded photo
• Open any MFE that calls hydrateAuthenticatedUser: true (profile, account, learner-dashboard)
• Confirm the header shows the initials avatar instead of a generic icon
• Upload a profile photo — confirm the header updates to the real photo
• Delete the photo — confirm the header returns to the initials avatar

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @SantiagoSuHe!

This repository is currently maintained by @openedx/committers-frontend.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.