Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Ldap] Deprecate '{username}' parameter use in favour of '{user_identifier}' in LDAP configuration#46683
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carsonbot commentedJun 16, 2022
Hey! I think@Jayfrown has recently worked with this code. Maybe they can help review this? Cheers! Carsonbot |
Jayfrown left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
lgtm
nicolas-grekas commentedJun 20, 2022
It looks like this would benefit from triggering a deprecation when |
wouterj commentedJun 20, 2022
I agree with@nicolas-grekas. There is no "forward compatibility" here, as we don't replace
It would be a good idea to change this parameter name though. That would mean replacing both (like you introduce this PR) and trigger a deprecation when Status: needs work |
ktherage commentedJun 29, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I made some changes based on your returns. This will allow a smoother change when droping deprecation notice IMO. |
wouterj left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I like your proposal of doing the cleaning up in theLdapBadge. I've left one comment in a place that is not directly dependent onLdapBadge, but other than that this is ready to go imho!
Uh oh!
There was an error while loading.Please reload this page.
4efdadb to1f11b3eCompare1f11b3e to76ed733Compare…ifier}' in LDAP configuration
76ed733 to6dd1221Compare
nicolas-grekas left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
(I just pushed the last changes)
fabpot commentedJul 29, 2022
Thank you@ktherage. |
Uh oh!
There was an error while loading.Please reload this page.
This PR aims to fix a missing forward compatibility as done in src/Symfony/Component/Ldap/Security/LdapUserProvider.php at line 80 when authenticating with LDAP and using the following configuration :
instead of :
maybe related to :#40403