Create Authentication Component

[darksnow]

Hi.

Any idea how to go about extending the CakePHP 2.x BaseAuthenticate so I can use LinkedIn as an Authentication supplier?

Essentially I'm looking to be able to login to my site using my LinkedIn ID and none of the plugins I've found seem to support this.

I'm happy to write this, but perhaps the code already exists, any pointers would be much appreciated.

Thanks.

Martin...

[ProLoser]

I haven't mesed with making custom Authentication modules in Cake2 yet, but after reading the docs, I think the best approach would be to simply supplement the Oauth Component (in the ApisDatasource Plugin) to include the functions expected (such as authenticate() ).

I'm not sure if you would be able to use Basic or Digest instead. This may be something I choose to implement for my own reasons in the near future however.

If you choose to undertake this, I will assist you with it as I could definitely benefit from it. The only caveat is that you will have to implement it on top of the ApiDatasource plugin so that all APIs (that can) may leverage it.

[darksnow]

Hi Dean.

Thanks very much for the quick reply.

I guess I'm a little confused looking at the code. The Oauth component
referenced Twitter a lot in the comments but the code itself appears to
be generic. While I could create an authenticate method in there next to
the authorize methos, I'm not entirely sure what yo put in it.

To add to my confusion, it appears like the Linkedin plugin already
supports this. In Linkedin/Config/Linkedin.php there is an explicit
reference to the authenticate call to the Linkedin API. I'm guessing
that I need to call that through the OAuth API somehow but looking at
your example code hasn't enlightened me any.

Sorry if I'm just not seeing something obvious here but it seems to me
that the code you already have in place does the authentication, just
not in a way easily integrated with the CakePHP 2.0 AuthComponent.
Looking at what you have, I'm guessing it will just be a couple of lines
of code in a couple if files, then I add Linkedin.Linkedin to my list of
authenticators and I'm away. I'm just not clear on where or what those
lines may be.

Thanks for the pointers so far and any help you can give. Once I
understand how this all works I'll be more than happy to flesh this out
and submit any code back to your plugin.

Cheers Dean.

Martin Fraser
darksnow.net

On Thu, 2012-05-17 at 16:18 -0700, Dean Sofer wrote:

I haven't mesed with making custom Authentication modules in Cake2 yet, but after reading the docs, I think the best approach would be to simply supplement the Oauth Component (in the ApisDatasource Plugin) to include the functions expected (such as authenticate() ).

I'm not sure if you would be able to use Basic or Digest instead. This may be something I choose to implement for my own reasons in the near future however.

---

Reply to this email directly or view it on GitHub:
https://github.com/ProLoser/CakePHP-LinkedIn/issues/3#issuecomment-5776588

[ProLoser]

So the reason all the comments are about twitter is because most of this takes some tips from @neilcrookes work with OAuth. The Auth component is actually an abstracted version of his twitter component

I do think it will be possible to integrate in just a few lines with the new Cake Auth, and yes it does use authentication, but that's to the API itself. I'm not sure if that's exactly the same thing, but you will probably be re-using those endpoints, yes.

It had also occurred to me that we probably cannot simply add the methods to this component since it must extend the Auth component, so we will probably have to make another one that is nearly identical. Ideally though we should try to make a one-component solution if possible.

I can try to cleanup the documentation, and now that I've recently switched back to CakePHP I will likely be cleaning up the Apis Plugin a little bit so that the implementation is more uniform across different providers. On a side note, I recommend watching this video I made that goes over a Node.js port of the ApisPlugin so that (at the very least) you can get an understanding of the design principal behind the ApiDatasource and Endpoint Maps I leverage. The code won't directly translate but it's very nearly identical.

[ProLoser]

Opened ProLoser/CakePHP-Api-Datasources#5 for this