Can't login to admin backend, since new security patch 2.4.4-p8

[Eddcapone]

Sometimes e.g. after the weekend, we suddenly can't login into the admin area / backend of our shop, since installing this security patch: https://helpx.adobe.com/security/products/magento/apsb24-18.html

We need to delete our cookies to be able to login again.

Error:

Argument #1 ($datetime) must be of type string, null given in /vendor/magento/module-security/Model/AdminSessionInfo.php:136

https://github.com/magento/magento2/blob/9721cc22eb32482d82e5e3d275fe3a0221d8b750/app/code/Magento/Security/Model/AdminSessionInfo.php#L136

This is how it used to be in 2.4-develop:

    $lastUpdatedTime = $lastUpdatedTime === null ? 0 : strtotime($lastUpdatedTime);

I don't have information on how to reproduce this.

[m2-assistant[bot]]

Hi @Eddcapone. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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-Dash. 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

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

Hi @Eddcapone

Thanks for reporting and collaboration.

Can you please share the details steps to reproduce the issue and screenshots in order for us to reproduce the issue accurately.

Thanks.

[Eddcapone]

@engcom-Dash As written here. I don't have informations on how to reproduce this. We just knows that it happens to us since we installed the patch. Last time it happend after the weekend.

[engcom-Dash]

Hi @Eddcapone

Thanks for reporting and collaboration.

We have a similar issue - 38704

Hence, we are considering this as a duplicate ticket and closing this ticket.

[Eddcapone]

@engcom-Dash Please explain how it is remotely similar. It has nothing to do with our issue.