[FLOW3-general] Extending default account - new authentication provider?

[Søren Malling]

Hi Andi,

I got some properties for the user account that is relevant to the
FLOW3 application I'm writing that isn't covered by the Party model
(ex. project -> ObjectStorage to another model of mine). Is there a
way to implement my own properties?

If not, I will use the TYPO3 LoginController as example

http://git.typo3.org/FLOW3/Packages/TYPO3.git?a=blob;f=Classes/Controller/LoginController.php;h=4b6007f9566b7c6589128bece83000d2801b99ed;hb=HEAD

but before i start, how do I "tell" the authenticationManager to use
my specific model and it's properties for authentication? Or isn't
that the case with TYPO3 V5?

Greets,

Søren Malling

TYPO3 Brugergruppe Danmark: www.typo3danmark.dk
Twitter: twitter.com/sorenmalling



On Mon, Jan 10, 2011 at 10:15 AM, Andreas Förthner
<andreas.foerthner at netlogix.de> wrote:
> Hi Søren,
>
> If you really need your own model, you will have to implement your own
> authentication provider. But an account is meant to hold only the account
> information, i.e. the credentials and roles needed for authentication and
> authorization respectively. For storing a name, e-mail etc. the party
> model should be used. By this structure it is also possible to have more
> than one account per party, e.g. a backend and a frontend account for the
> same person.
>
> I hope this helps.
>
> Greets Andi
>
> Am 10.01.11 08:09 schrieb "Søren Malling" unter <soren.malling at gmail.com>:
>
>>Hi,
>>
>>I'm currently working with the security framework of FLOW3 - I must
>>say it's amazing! And I'm learning a lot of new stuff from the
>>project!
>>
>>RIght now I'm facing the need of "extending" the default account
>>model. I need to add some informations like firstname, lastname and
>>e-mail (All these properties are available in the Party Person model).
>>How will I be able to extend the \F3\FLOW3\Security\Account model?
>>
>>I've had a look at how the PhoenixDemoTypo3Org.git package are using
>>the security/account functions along with the Registration plugin. It
>>looks like it made a new authentication provider (from
>>Configuration/Settings.yaml):
>>
>>FLOW3:
>>  security:
>>    authentication:
>>      providers:
>>        DefaultProvider:
>>          providerClass: PersistedUsernamePasswordProvider
>>          entryPoint:
>>            webRedirect:
>>              uri: typo3/login
>>      authenticationStrategy: oneToken
>>  mvc:
>>    notFoundController: F3\TYPO3\Controller\ErrorController
>>
>>Is this the way to go, in order to use my own account model?
>>
>>Best regards,
>>
>>Søren Malling
>>
>>TYPO3 Brugergruppe Danmark: www.typo3danmark.dk
>>Twitter: twitter.com/sorenmalling
>>
> Dipl.-Inf. Andreas Förthner
> Leiter Web-Entwicklung
>
> Telefon: +49 (911) 539909 - 0
> E-Mail: andreas.foerthner at netlogix.de
> Internet: http://media.netlogix.de
>
> --
> netlogix GmbH & Co. KG
> IT-Services | IT-Training | Media
> Andernacher Straße 53 | 90411 Nürnberg
> Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
> E-Mail: mailto:info at netlogix.de | Internet: http://www.netlogix.de/
>
> netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
> Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
> Umsatzsteuer-Identifikationsnummer: DE 233472254
> Geschäftsführer: Stefan Buchta, Matthias Schmidt
>
> _______________________________________________
>
>
>>FLOW3-general mailing list
>>FLOW3-general at lists.typo3.org
>>http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
>
>
> _______________________________________________
> FLOW3-general mailing list
> FLOW3-general at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
>