Needs work
Project:
Drupal core
Version:
main
Component:
other
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Feb 2020 at 10:21 UTC
Updated:
11 Dec 2021 at 02:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sandeep_jangra commentedI have found a temporary solution after passing provider id in rest header.
Comment #3
sandeep_jangra commentedComment #4
swentel commentedThis is how it's designed, so what you ask is a feature (interesting one though).
Comment #5
sandeep_jangra commentedComment #6
sandeep_jangra commentedUpdate patch file
Comment #7
hardik_patel_12 commentedComment #10
bradjones1At 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...