Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The auth_adapters config option is using an associative array with integer keys. An list array will cause unwanted results. #99

Open
visto9259 opened this issue Oct 8, 2024 · 0 comments
Labels
bug Something isn't working V3 To be fixed in version 3
Milestone

Comments

@visto9259
Copy link
Member

In the lmc_user config, the key auth_adapters is expecting an associative array with the following signature:

'lmc_user' => [
   'auth_adapters' => [
        100 => 'firtsadaptername`,   // where 100 is the priority and is an integer
        200 => 'secondadaptername',
   ],
]

if one was to pass a list array, then it would be treated the same as:

'lmc_user' => [
   'auth_adapters' => [
        0 => 'firtsadaptername`,   
        1 => 'secondadaptername',
   ],
]

Althought, it would defeat the purpose to use a list array, there should be a assertion in the factory to detect and reject list arrays.

@visto9259 visto9259 added the bug Something isn't working label Oct 8, 2024
@visto9259 visto9259 added the V3 To be fixed in version 3 label Oct 8, 2024
@visto9259 visto9259 added this to the 3.7.1 milestone Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working V3 To be fixed in version 3
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant