mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 12:45:52 +03:00
[GH-ISSUE #678] How to handle oauth_verifier manually ('oob' callback URL) #439
Labels
No labels
bug
cocoapod
duplicate
enhancement
feature-request
help wanted
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/OAuthSwift#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zisoft on GitHub (Oct 7, 2021).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/678
I'm developing a plugin for a MacOS application which will use the Flickr API.
Because this is only a plugin I cannot provide an own URL scheme for the callback so according to the OAuth1 spec I set 'oob' (out-of-band) for the callback URL.
So I implemented the following steps:
This works as expected, the Flickr authorize page is opened in the browser and after approving permissions I get the verifier code displayed on that page. With this verifier I now need to call the accessTokenUrl.
I cannot figure out how to manually set the oauth_verifier in client.credentials because it is readonly.
EDIT:
I have declared open the
OAuthSwiftCredential.oauthVerifierproperty as well as theOAuth1Swift.postOAuthAccessTokenWithRequestTokenmethod. Now I can manually set the oauth_verifier value after authorize and then call the accessTokenUrl. But I'm curious to know if I'm the only one who uses this workflow?@sk-chanch commented on GitHub (Jun 22, 2022):