When i am trying to use two different contributed module at the same time name "simple_auth" and "JWT", then authentication manager provide incorrect provider id. Authentication Manager provide provider_id based on priority not on request.

Comments

sandeep_jangra created an issue. See original summary.

sandeep_jangra’s picture

StatusFileSize
new933 bytes

I have found a temporary solution after passing provider id in rest header.

sandeep_jangra’s picture

StatusFileSize
new1.26 KB
swentel’s picture

Category: Bug report » Feature request
Priority: Critical » Normal

This is how it's designed, so what you ask is a feature (interesting one though).

sandeep_jangra’s picture

Category: Feature request » Bug report
sandeep_jangra’s picture

StatusFileSize
new1.26 KB

Update patch file

hardik_patel_12’s picture

Status: Needs work » Needs review

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

bradjones1’s picture

Version: 9.2.x-dev » 9.4.x-dev
Category: Bug report » Feature request
Status: Needs review » Needs work

At the very least this needs discussion about approach; a read of #6 indicates the client can request use of a particular authentication provider by name, which is... interesting and basically circumvents the resolution through the ::applies() method on the providers.

It sounds like the real intent here is to support two authentication providers for the same type of authentication? In that case, it seems like it would be incumbent on the site owner to provide something like a meta-provider that resolves which to use based on some type of business logic. But then again, that's in theory what the priorities are for.

I was going to change the title but I'm not sure what I would even call that...

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.