Thank you for your question!
Twitter adheres to OAuth1.0a protocol. The most interesting part that has to be implemented client-side is the signing the request and send it to Twitter, in order to obtain the access token and the token secret for the user and pass them to Backend Services. You are right that there are a lot of recommendations to do this server-side. There are also a lot of community threads on this. A base line there are really the security issues in the client-side implementation and the use of external JS libraries for this.
In order to test the Backend Services part of the overall user authentication:
- Register an app with the developer section of Twitter (requires consumer Twitter registration and verified mobile number for this account).
- Obtain the API key and API secret for the app and place them into the backend project under Settings > User authentication > Twitter
- Obtain the access token and token secret from Twitter for you own acount
- Make a request to Backend Services API with them
- You are already registered into the Users section of the backend services project (note that Twitter will not provide the email of a user)
Please, let us know if you have further questions!
Everlive is now Telerik Backend Services
, and is part of the Telerik Platform
. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar
on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)