I am currently setting up a user management area for my application and would like to write my own User class.
This class should extend/relate to the Account to add some additional fields (e.g. last_login etc.) for my user.
Naturally I would have installed the Party package and would have created my own User class extending the AbstractParty.
But as the setParty/getParty methods in Account are marked as deprecated I wonder how my (rather common) use case is designated instead?
Is there a best practice that replaces the usage of the deprecated setParty/getParty methods?
I don’t want to rely on methods that may be abandoned soon but I don’t want to rewrite all of the methods that make use of the \TYPO3\Flow\Security\Account(Repository) classes directly (e.g. PersistedUsernamePasswordProvider) either.
I have found this old forum entry with further urls but all of those either don’t extend the Account or still make use of the getParty method… https://forum.typo3.org/index.php/t/202180/