PHP Classes

Oauth 2.0: Support for section 2.3.1

Recommend this page to a friend!

      PHP OAuth Library  >  PHP OAuth Library package blog  >  How to Implement PHP ...  >  All threads  >  Oauth 2.0: Support for section 2.3.1  >  (Un) Subscribe thread alerts  
Subject:Oauth 2.0: Support for section 2.3.1
Summary:Does the App support Section 2.3.1 for Oauth 2.0
Messages:23
Author:dhairy
Date:2014-04-18 15:11:11
Update:2014-07-13 01:58:11
 
  1 - 10   11 - 20   21 - 23  

  21. Re: Oauth 2.0: Support for section 2.3.1   Reply   Report abuse  
Picture of Manuel Lemos Manuel Lemos - 2014-07-13 01:58:11 - In reply to message 20 from Tadej
No, the idea is to make a dumb API call when the token expires, assuring that all simultaneous clients are stopped.

Anyway, do not worry, in the worst case of two simultaneous clients trying to refresh an expired token, only one will succeed.

Your application should be ready for failed API calls because those happen much more frequently due to outages of the API server. That is very common with Facebook, so you should be able to deal with those failures.

  22. Re: Oauth 2.0: Support for section 2.3.1   Reply   Report abuse  
Picture of Tadej Tadej - 2014-09-28 11:26:55 - In reply to message 11 from Manuel Lemos
I saw there were some changes made to this library, and I was wondering if there is any way this feature is already supported?

  23. Re: Oauth 2.0: Support for section 2.3.1   Reply   Report abuse  
Picture of Manuel Lemos Manuel Lemos - 2014-09-30 02:00:09 - In reply to message 22 from Tadej
Sorry I did not do it before because I could not figure a clean way to implement that authorization flow.

I have implemented it now. Take a look at the login_with_twitter2.php example script to see how configure the client_credentials authorization flow.

 
  1 - 10   11 - 20   21 - 23