starred/OAuthSwift

Fork 0

mirror of https://github.com/OAuthSwift/OAuthSwift.git synced 2026-04-26 12:45:52 +03:00

[GH-ISSUE #374] No apparent way to make Oauth 1.a requests #238

New issue

Closed

opened 2026-03-03 16:46:58 +03:00 by kerem · 7 comments

kerem commented

2026-03-03 16:46:58 +03:00

Owner

Originally created by @josephquigley on GitHub (May 17, 2017).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/374

Description:

There doesn't seem to be any way to make OAuth 1.a requests in the wiki, example code, or in source. Are people supposed to use raw OAuthSwiftHTTPRequest requests?

OAuth Version:

Version 1
Version 2

Originally created by @josephquigley on GitHub (May 17, 2017). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/374 ### Description: There doesn't seem to be any way to make OAuth 1.a requests in the wiki, example code, or in source. Are people supposed to use raw `OAuthSwiftHTTPRequest` requests? ### OAuth Version: - [x] Version 1 - [ ] Version 2

kerem closed this issue

2026-03-03 16:46:58 +03:00

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@phimage commented on GitHub (May 17, 2017):

I am a little confusing about why you did not find the code, maybe I do not understand your question
But there a lot of ´get´ in demo app
In readme there is an example of request

@phimage commented on GitHub (May 17, 2017): I am a little confusing about why you did not find the code, maybe I do not understand your question But there a lot of ´get´ in demo app In readme there is an example of request

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@josephquigley commented on GitHub (May 20, 2017):

Thought I replied to you, but it looks like email reply-to didn't work. Sorry.

I'm new to OAuth, so forgive my questions. Are you referring to the signed request part of the readme? Because the OAuth1 section doesn't show any examples of a 1.0a request that only uses a public key and a secret key. It shows examples of tokens and authorize URLs. As far as I know, those don't apply to 1.0a.

@josephquigley commented on GitHub (May 20, 2017): Thought I replied to you, but it looks like email reply-to didn't work. Sorry. I'm new to OAuth, so forgive my questions. Are you referring to the signed request part of the readme? Because the OAuth1 section doesn't show any examples of a 1.0a request that only uses a public key and a secret key. It shows examples of tokens and authorize URLs. As far as I know, those don't apply to 1.0a.

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@phimage commented on GitHub (May 20, 2017):

I don't think so
1.0a also could use authorize
https://oauth.net/core/1.0a/

@phimage commented on GitHub (May 20, 2017): I don't think so 1.0a also could use authorize https://oauth.net/core/1.0a/

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@josephquigley commented on GitHub (May 22, 2017):

Authorize in OAuthSwift?

@josephquigley commented on GitHub (May 22, 2017): Authorize in OAuthSwift?

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@phimage commented on GitHub (May 23, 2017):

oauthswift.authorize(... , normal use of framwork, see readme...

@phimage commented on GitHub (May 23, 2017): `oauthswift.authorize(...` , normal use of framwork, see readme...

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@josephquigley commented on GitHub (May 29, 2017):

Ok, I figured it out. The documentation on the Readme.md was not clear. You can init OAuth1Swift with empty strings for the requestTokenUrl, authorizeUrl, and accessTokenUrl parameters.

Pull request: https://github.com/OAuthSwift/OAuthSwift/pull/378

@josephquigley commented on GitHub (May 29, 2017): Ok, I figured it out. The documentation on the Readme.md was not clear. You can init `OAuth1Swift` with empty strings for the `requestTokenUrl`, `authorizeUrl`, and `accessTokenUrl` parameters. Pull request: https://github.com/OAuthSwift/OAuthSwift/pull/378

kerem commented

2026-03-03 16:46:59 +03:00

Author

Owner

@phimage commented on GitHub (Jun 2, 2017):

@josephquigley do not close your issue next time if you make a PR
Just put Fix #issue_number in your PR title and the issue will be closed automatically when merging PR

@phimage commented on GitHub (Jun 2, 2017): @josephquigley do not close your issue next time if you make a PR Just put Fix #issue_number in your PR title and the issue will be closed automatically when merging PR

kerem referenced this issue

2026-03-03 16:49:33 +03:00

[PR #238] [MERGED] Support for Device Flow Authentication #582