Magento 2.3.3 issue with login admin related offset 2 Encryptor

[mrtuvn]

Preconditions (*)

1. Magento 2.3.3
2. PHP 7.1.24

Steps to reproduce (*)

Expected result (*)

Login admin without problem

Actual result (*)

Got notice error show undefine offset 2 in file Magento\Framework\Encryption\Encryptor.php Line 590

[m2-assistant]

Hi @mrtuvn. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@mrtuvn do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[manishmittalm]

Hello @magento

Team please provide me magento 2.3.3

[m2-assistant]

Hi @manishmittalm. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[manishmittalm]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @manishmittalm. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @manishmittalm, here is your Magento instance.
Admin access: https://i-25025-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[manishmittalm]

Thanks @magento for sharing. Can you confirm PHP version for this shared instance.

[manishmittalm]

@mrtuvn
Magento 2.3.3 supports
PHP ~7.1.3
~7.2.0
~7.3.0

Please check with these versions. It not support PHP 7.1.24

[mrtuvn]

ok i fixed my problem. Change php to php7.2 and problem gone
Please close this one

[m2-assistant]

Hi @krishprakash. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[krishprakash]

Not reproduced.
Closing this issue

[hostep]

Just for completeness sake, this is a duplicate of #23511

I tried explaining the case where this problem can happen in #23511 (comment)

If you are able to get the php sodium extension running with PHP 7.1, it might still work. But upgrading to 7.2 or even 7.3 is better since it is supported for a longer period.

[SolsWebdesign]

Clean install on Magento 2.3.3 on NginX (hypernode) with php 7.2.19 (to be precise v7.2.19-1).
Set in Developer mode, added Sample data using bin/magento sampledata:deploy and tried to login:
1 exception(s):
Exception #0 (Exception): Notice: Undefined offset: 2 in ../vendor/magento/framework/Encryption/Encryptor.php on line 590

Tried to create another admin through CLI but same error.
That is weird... is it because of the sample data?
Started a fresh 2.3.3 on NginX (hypernode) with php 7.2.19 and left the sample data. But did set it to developer mode. Same error :-(
What ever I try I get this. This should not happen on a clean install with PHP 7.2, right? Or am I missing something here?

[edit] okay, downgraded php from 7.2.19 to 7.1.27, cleared cache, run setup upgrade, etc... created new admin user and... am able to login. Tried with both sample data and without, no difference...

So clean install Magento 2.3.3 on NginX (hypernode) with php 7.2.19 is the problem. It works fine on PHP 7.1.27....

Got Magento 2.3.3 working on PHP 7.1.27 and I can actually login (very important) and now try to install the sample data using bin/magento sampledata:deploy and...

Your requirements could not be resolved to an installable set of packages.
Problem 1
- doctrine/lexer 1.1.0 requires php ^7.2 -> your PHP version (7.1.27) does not satisfy that requirement. (etc etc etc).

okay... got it working. Clean install Magento 2.3.3 on NginX (hypernode) with php 7.1.27 and login! Leave browser with logged in administrator open (very important) and change PHP through ssh to PHP 7.2.19. When done, update password in the still open browser for the logged in administrator!

Refresh cache. I can now logout and log back in and install sample data and continue my work. I still think this should not happen on a clean install.