Authentication support
You need to be logged in to post messages in the forums. New users may register here.
|
Jérôme Vieilledent
Member since:
09 January 2008
Posts: 98
|
Thursday 07 July 2011 2:51:39 pm
Hello Damien
Now Autostatus supports OAuth authentication for Twitter and identi.ca, that's nice.
However, the way it's implemented avoid other authentication methods (like OAuth2 for Facebook). Indeed, in autostatusType::customWorkflowEventHTTPAction(), you force the use of Zend_Oauth_Consumer which only supports OAuth 1.
A nice thing would be to allow to define an authenticator per social network. The social network class would define a method returning the right authenticator for instance.
What do you think ?
|
|
|
Damien Pobel
Member since:
19 September 2005
Posts: 40
|
Friday 08 July 2011 11:25:31 pm
That seems to be a good idea but that also means that all authenticators should implement the same Interface and have a close system (same method calls/steps)
Is it possible given the differences between OAuth 1.0a and 2.0? I don't know OAuth 2.0 enough to answer :-)
Another solution would be to have a specific "custom workflow action" depending on the auth mechanism to use on a given social network. Since, this part is loaded with an Ajax request [1], this is quite easy to achieve. I know this is a bit procedural and this also means that a autostatus/oauth2 view will be required. On the other side, this would be very flexible if one day we need to implement another authentication system.
In fact, it really depends on the differences between OAuth 1.0a and 2.0. So I'll let you choose the wiser solution :-)
[1] https://github.com/dpobel/autosta...sses/autostatusajaxfunctions.php#L29
Cheers
|
|
You need to be logged in to post messages in the forums. New users may register here.
