I've been having major difficulties using this module and have reverted to reading the IETF specs for Oauth. Please can you inform how much of the specifications 1.0 and 1.0a have been implemented and fully tested. Are their tests available for use on each new release to ensure that subsequent releases dont break the code?

Do you have a roadmap for the development of 2.0. I am very happy to take on testing responsibilities and automate testing for each release.

Is there any dev sync'ing betweeen this module and other oauth modules?

I hope you can help me with a few queries:

I am a little unclear how this module implements the service, client, and resource owner in the spec.

I am unsure how to use the user consumer/secret table. Are all of the consumer credentials pooled but oauth and use in a client call? What is the workflow from here? How does Oauth use credentials? Does a client use these to initiate the oauth workflow?

What does "An API for providing historical versions of a services API." do?

If Oauth 2.0 is only roadmapped at present what is the implementation in the latest dev release and does it work?

thanks

Comments

juampynr’s picture

juampynr CreditAttribution: juampynr commented

Sure, please give a hand to help this issue queue to move on. I also want to add tests to this module but first I need to find out what is the top priority at the moment.

Regarding your questions, here are my answers. Note that although I am a maintainer, I have done very little so far but I have started to pay attention recently.

Are their tests available for use on each new release to ensure that subsequent releases dont break the code?

No. But tests are something that this module really needs.

Do you have a roadmap for the development of 2.0. I am very happy to take on testing responsibilities and automate testing for each release.

No AFAIK.

Is there any dev sync'ing betweeen this module and other oauth modules?

No.

I am a little unclear how this module implements the service, client, and resource owner in the spec.

Are you actually missing documentation? That would be our starting point to get that clear.

I am unsure how to use the user consumer/secret table. Are all of the consumer credentials pooled but oauth and use in a client call? What is the workflow from here? How does Oauth use credentials? Does a client use these to initiate the oauth workflow?

I do not know about that yet.

What does "An API for providing historical versions of a services API." do?

No idea, but it sounds scary. Where did you read that?

If Oauth 2.0 is only roadmapped at present what is the implementation in the latest dev release and does it work?

It uses OAuth 1.

juampynr’s picture

juampynr CreditAttribution: juampynr commented
Status: Active » Closed (won't fix)

Closing issue.