[Test failure] <TC-00003>: <Warning message omits user email in activation prompt>

[SantiagoSuHe]

Release

Ulmo

Expected behavior

When a user who already has an account but has not validated their email tries to log in again, the LMS should display the standard activation warning message, including the email address where the activation link was sent.
Example:
“We just sent an activation link to user@example.com.”

Actual behavior

The warning message is displayed, but the email address is missing.
Instead of rendering the user’s email, the message shows only a period (“.”).
This can be clearly seen in the attached screenshot, where the message reads:

“We just sent an activation link to .”

The UI renders correctly, but the dynamic value for the email is missing.

Steps to reproduce

1. Create a new account using a valid email address.
2. Do not verify the email.
3. Return to the LMS login page.
4. Enter the same username/email and password.
5. After submitting, observe the activation warning message.
6. Note that the email portion of the message is omitted, showing only a dot.

Additional information

This is happening in TEAK too

[BryanttV]

Hi @SantiagoSuHe, thanks for the report!

I was testing in the sandbox, and indeed, the email is not being displayed in the message. However, in the endpoint response, it seems that the email is available:

The endpoint response looks like this:

{
  "success": false,
  "value": "None",
  "error_code": "inactive-user",
  "context": {
    "platformName": "Open edX Ulmo Demo",
    "supportLink": ""
  },
  "email": "bryann.valderrama@edunext.co"
}

However, in the Auth MFE, we are accessing context.email. It seems that simply changing that to email should solve the problem.

[BryanttV]

I found the problem in the Authn MFE. When we are accessing the action.payload, the object looks like this:

{
    "loginError": {
        "success": false,
        "value": "None",
        "errorCode": "inactive-user",
        "context": {
            "platformName": "Your Platform Name",
            "supportLink": ""
        },
        "email": "user@example.com"
    }
}

Therefore, email does not exist (and neither does redirectUrl) at the root level. It's inside loginError. One possible solution would be to replace that line with:

const { loginError } = action.payload;
const { email, redirectUrl } = loginError;

With that change, the email is now displayed correctly in the error message.

[bradenmacdonald]

This looks like an issue with the auth MFE, not the authoring MFE. Should I move it?