Update README to include Single-User Auth Info #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I just upgraded to the V3 API (very nice job), but I was a little confused on authenticating. I only ever needed to authenticate as a single user, and thus didn't need to go through the hassle of building multi-user authentication. This information wasn't in this repo, so I had to go digging and found out about single-user auth on the Vimeo documentation on the API site. I feel like this is probably a common enough occurance to warrant placing it in the readme. I retrieved all text from the Vimeo API site.
| @@ -87,6 +87,18 @@ $lib->setToken($token->access_token) | |||
| ### Authenticated | |||
|
|
|||
|
|
|||
| #### Single User Applications | |||
|
|
|||
| If you only ever plan on interacting with a single user account feel free to hard code your access tokens into your app. This token should follow the spec described under authenticated requests. | |||
There was a problem hiding this comment.
Lets drop the second sentence, and just keep it as...
If you only ever plan on interacting with a single user account, feel free to hard code (or preferably configure) your access tokens into your app.
|
|
||
| ```php | ||
| $lib->setToken($access_token); | ||
| ``` |
There was a problem hiding this comment.
@Dashron this look good - or do you want the code example gone too?
There was a problem hiding this comment.
Definitely keep the example. This looks good.
Just fill out our CLA (keeps the code licensing clear): developer.vimeo.com/cla and I'll merge this in.
|
+1! |
|
Yes |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just upgraded to the V3 API (very nice job), but I was a little confused on authenticating. I only ever needed to authenticate as a single user, and thus didn't need to go through the hassle of building multi-user authentication. This information wasn't in this repo, so I had to go digging and found out about single-user auth on the Vimeo documentation on the API site.
I feel like this is probably a common enough occurance to warrant placing it in the readme. I retrieved all text from the Vimeo API site.