Magento 2.4.8-p3 appear admin redirect

[felix-qing]

Preconditions and environment

• Magento version：2.4.8-p3
• I use it on Windows.
• mariadb 11.4
• opensearch 3.3.2

Steps to reproduce

question

it's new project. After compilation and deployment,start the project

php -S 127.0.0.1:8085 -t pub

I went to admin,Click to Sign in I didn't find any errors; it was just like refreshing the page. I found a reference, but it didn't work at all. website

This is not a session issue.

I found the metadata directory.

If I delete all files in the metadata directory,I clicked Sign in and was able to access the admin page.

other thing

If I don't delete the files in the metadata directory,I found this Path as follows

/admin/admin/auth/login/key/

If I delete the files in the metadata directory,I found this Path as follows

/admin/admin/index/index/key

so what heppened?

Expected result

enter the admin page

Actual result

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @felix-qing. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @felix-qing ,

Thank you for the report and for your collaboration.

We attempted to reproduce the issue on our side, but were unable to replicate the behavior.

To proceed further, could you please provide a few additional details or steps that may help us reproduce the issue?

For now, we are marking this ticket as "Needs Update."

Thank you!

[engcom-November]

Hello @felix-qing ,

Kindly following up on above comment. Thank You!