"CurrentSecurityContextArgumentResolver" does not support property population of different types.

[milo-xiaomeng]

Expected Behavior

The CurrentSecurityContextArgumentResolver should be capable of supporting property population of different types, meaning it should be able to map information from the security context onto parameters of varying types in controller methods.

Current Behavior

Currently, the CurrentSecurityContextArgumentResolver does not support the functionality of cross-type property population, resulting in data retrieved from the security context being unable to directly populate objects with properties of different types.

Context

This stems from our desire to leverage user information, acquired from the security context, throughout diverse business logics. We have indeed deliberated on the option of devising a bespoke resolver. However, this approach would inevitably introduce greater intricacy into our code and amplify the overheads tied to its upkeep. Presently, my strategy involves harnessing the ConversionService provided by the Spring framework's context. In scenarios where there are inconsistencies between types, conversions are seamlessly executed via the ConversionService, ensuring that the data can be appropriately utilized regardless of initial type disparities.