You have requested a non-existent service "openid_connect.openid_connect".

Thanks for the report @a.crowe_drupal. Can you apply the patch from MR #144? I believe this is a duplicate of #3462532.

Hi,

After update 1.4 to 3.0.0-alpha6 I got the same error :

Error Output:                                                                                        
  ================                                                                                     
                                                                                                       
  In ContainerBuilder.php line 992:                                                                    
                                                                                                       
    You have requested a non-existent service "openid_connect.openid_connect".

D10.3.14
Drush 12
Exteralauth enabled

@jérôme dehorter... Do you get the same error if you upgrade from 1.4 to the 3.x-dev version?

Hi @pfrilling,
Yes, I upgrade from 1.4.0 to 3.0.0@alpha6.

To avoid this problem, you need to perform a two-step update:
1 - Uninstall the module and update the configuration.
2 - Deploy to update the database.
3 - Export the database and use it for the following steps.
3 - Delete the module in version 1.4.0
4 - Install version 3.0.0@alpha6
5 - Enable Externalauth and OpenID.
6 - Save the configuration changes.
7 - Deploy a second time.

Are you able to try to upgrade from 1.4 to 3.x-dev and report if the same steps are required when upgrading to 3.0.0@alpha6? The latest development version has the fix for the non-existent service included.

Hi @pfrilling,
Yes, I upgrade from 1.4.0 to 3.x-dev.
I'm going to install the latest patch on version 3.0.0-alpha6 to test if it works.
A new working version is required for this to be deployed to production.

Hi,
I tried reverting to the latest patch, but it didn't work.

Installation is possible with the development version. On my local machine, I have no issues, but on our AWS environments, I have the following problem:
The service "openid_connect.openid_connect" has a dependency on a non-existent service "externalauth.authmap".

Hi,
I tried to install commit 3.x-dev#6052cff18ea87ee3e801cdc2546739b99e198f31 and it's the same, good on local but not on AWS.

Running into the same problem when upgrading from 1.4 to 3alpha6 :

You have requested a non-existent service "openid_connect.openid_connect".

Dev version does not solve the problem.

Edit : 3.0.0-alpha5 DOES SOLVE the problem.

@nicocin,
Thanks for the tips, 3.0.0-alph5 solve my problem.

Thanks for the reports. Just to confirm...

• Upgrading from 1.4 to 3.0.0-alpha5 works.
• Upgrading from 1.4 to 3.0.0-alpha6 (or greater) does _not_ work.

Am I understanding that correctly?

---

Once you are on 3.0.0-alpha5, does the upgrade to 3.0.0-alpha6 work?

Perhaps when testing a code change we should recommend using drush deploy -v to make user testing more predictable? Here is a link to the order it run in https://www.drush.org/13.x/deploycommand

Hi @pfrilling,
Yes, that's right, upgrading from 1.4 to 3.0.0-alpha6

I confirm no issues with alpha5, alpha6 on the other hand creates that issue

I have the same issue. I am on Drupal 10.5.x, currently use openid_connect 1.4, and want to update to 3.0.0-alpha6. I have custom services which use openid_connect.
So currently, externalauth module is not enabled and authmap table does not exist.

When i try drush updb, i have the error : You have requested a non-existent service "openid_connect.openid_connect".

Main difference between 3.0.0-alpha5 and 3.0.0-alpha6 is autowiring.

Finally found a way altering the service provider to not remove openid_connect service if externalauth module is not enabled yet, but remove arguments so externalauth is not called anymore during bootstrap if it does not exist.

class OpenidConnectServiceProvider extends ServiceProviderBase {

  /**
   * {@inheritdoc}
   */
  public function alter(ContainerBuilder $container) {
    // This service was introduced as a new dependency in version 2.0alpha3.
    try {
      $container->getDefinition('externalauth.authmap');
    }
    // If the service is not available, remove its dependent services.
    catch (ServiceNotFoundException $exception) {
      // Requires 'externalauth.authmap'.
      $openid_connect = $container->getDefinition('openid_connect.openid_connect');
      $openid_connect->replaceArgument('$authmap', NULL);
      $openid_connect->replaceArgument('$external_auth', NULL);
    }
  }

}

MR177 is only here to be able to patch 3.0.0-alpha06

MR177 works perfectly on `3.0.0-alpha6` version on production servers.

I was wondering if the patch was only necessary during the migration process?

I was wondering if the patch was only necessary during the migration process?

Yes. After you're up-to-date, you shouldn't need it.

I updated MR 176 to include some deprecation messaging for removal at a later date and plan to merge it to ensure the 1.x upgrade path succeeds without having to patch. If I can get a second review on those changes, I'll get it merged in.