[TYPO3-dev] Graphical OpenID selector vs. login form

[Ernesto Baschny]

Christian Weiske schrieb am 06.08.2013 08:55:

> I made a patch that adds (customizable0 OpenID provider buttons to the
> login form. Helmut rather likes to see that in a separate extension
> than in the core itself.
> 
> Unfortunately, the login form is not dynamic at all; hooking into it is
> impossible (unless you XCLASS \backend\Controller\LoginController
> somehow). I had to patch sysext/t3skin, systext/openid and
> sysext/backend to make the provider buttons work.
> 
> Moving the icons to an extension would also other extensions to be
> developed, e.g. to include the new AccountChooser[3] the OpenID Working
> group is developing.
> 
> So, how should the backend login form be made extensible?
> - Do you think XCLASSing is enough?
> - Do we need to support multiple login forms beside each other,
>   switchable by buttons?
> 
> Maybe it's enough to allow backend login form services to provide
> HTML, JS and CSS for their own login form. The login form controller
> would simply render them in HTML, add switch buttons and take care of
> showing/hiding the particular login form.
> 
> 
> [1] http://forge.typo3.org/issues/49399
> [2] https://review.typo3.org/22577
> [3] http://accountchooser.net/

I would also love to see the login form expandable by hooks, so that we
could also get rid of the "hardcoded" OpenId specific parts (i.e.
"CSS_OPENIDCLASS" etc) that are part of the backend extension and t3skin
currently.

Kind regards,
Ernesto


-- 
Ernesto Baschny
TYPO3 CMS Core Developer
Release Manager TYPO3 4.5 & 6.2 LTS

TYPO3 .... inspiring people to share!
Get involved: typo3.org