[PR #192] [CLOSED] Use custom authorisation scheme #556

New issue

Closed

opened 2026-03-03 16:49:25 +03:00 by kerem · 0 comments

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/OAuthSwift/OAuthSwift/pull/192
Author: @p-salmon
Created: 2/24/2016
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (6)

853c5b4 Pull OAuthSwift
5b6f119 Pull OAuthSwift
f3e0254 Up
248dcd7 Merge pull request #1 from OAuthSwift/master
bfa72a0 Custom parameters for authorisation
0905d0f Merge branch 'master' of https://github.com/Poupouch/OAuthSwift

📊 Changes

3 files changed (+8 additions, -6 deletions)

View changed files

📝 OAuthSwift/OAuthSwiftClient.swift (+2 -1)
📝 OAuthSwift/OAuthSwiftHTTPRequest.swift (+2 -2)
📝 OAuthSwiftDemo/ViewController.swift (+4 -3)

📄 Description

We experienced some bug using LinkedIn OAuth and the "Authorization" header. Turns out this bug disappear if we use the parameter "oauth2_access_token" instead. This brings us to think about this correction.

I want to be able to use my own authorisation method using custom params. See LinkedIn Demo for example.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OAuthSwift/OAuthSwift/pull/192 **Author:** [@p-salmon](https://github.com/p-salmon) **Created:** 2/24/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (6) - [`853c5b4`](https://github.com/OAuthSwift/OAuthSwift/commit/853c5b4af35b60ab18c69f71acb5179ee5b053af) Pull OAuthSwift - [`5b6f119`](https://github.com/OAuthSwift/OAuthSwift/commit/5b6f1192c5444e0df8723dc4c965155b35b5197a) Pull OAuthSwift - [`f3e0254`](https://github.com/OAuthSwift/OAuthSwift/commit/f3e0254e5a0fabb7c17e0b68535bfee1f63b1efb) Up - [`248dcd7`](https://github.com/OAuthSwift/OAuthSwift/commit/248dcd7f098ce77e96a76a63f2747fa43a530d0c) Merge pull request #1 from OAuthSwift/master - [`bfa72a0`](https://github.com/OAuthSwift/OAuthSwift/commit/bfa72a0609d2ead6eccf0cc541fb9948a900b101) Custom parameters for authorisation - [`0905d0f`](https://github.com/OAuthSwift/OAuthSwift/commit/0905d0f91293b04ad3347aa109cf3b8650a821b5) Merge branch 'master' of https://github.com/Poupouch/OAuthSwift ### 📊 Changes **3 files changed** (+8 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `OAuthSwift/OAuthSwiftClient.swift` (+2 -1) 📝 `OAuthSwift/OAuthSwiftHTTPRequest.swift` (+2 -2) 📝 `OAuthSwiftDemo/ViewController.swift` (+4 -3) </details> ### 📄 Description We experienced some bug using LinkedIn OAuth and the "Authorization" header. Turns out this bug disappear if we use the parameter "oauth2_access_token" instead. This brings us to think about this correction. I want to be able to use my own authorisation method using custom params. See LinkedIn Demo for example. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>