yoobin_mion

Hi @rwinch , Thank you for your guidance on this. I initially chose the dot notation approach because it offers a simple and intuitive solution specifically for the nested user-name-attribute...

Hello @rwinch, I'd like to clarify your feedback on my PR about supporting nested properties in the user-name-attribute. Did you mean that I should implement support for expressions like `#{data.username}`...

Hi! @rwinch I've implemented the first part of your suggestion - adding the `username` field to `DefaultOAuth2User` and the `withUsername()` static factory method. For backward compatibility, I kept the `nameAttributeKey`...

Hi @rwinch thank you for the detailed guide. I've implemented the SpEL-based approach as outlined in the original issue. The solution provides - SpEL expressions for nested property access (e.g.,...

Thanks for the feedback @rwinch ! I've addressed all the review comments and updated the code accordingly. But the build failure appears to be related to Kotlin version. What would...

Hi @rwinch. I've addressed all the review feedback and updated the documentation as requested. Please let me know if there are any areas in the documentation that need further improvement...

Thank you for the review @rwinch ! I'm planning to create a separate commit to address the deprecated constructor/method usage you mentioned. However, I have a few questions that came...

Thank you for the guidance, @rwinch ! I've updated the deprecated constructor/method usage **in main** based on your review feedback. After searching through the codebase, I found that most of...

Hi @rwinch, I noticed that the "What's New" documentation for Spring Security 7 has recently been updated, which caused a conflict with the changes I previously added. I've resolved the...

Thanks for the rebase and I understood about the blocking issues.