Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/chimehq/oauthenticator
OAuth 2.0 request authentication
https://github.com/chimehq/oauthenticator
oauth oauth2 oauth2-client swift
Last synced: about 10 hours ago
JSON representation
OAuth 2.0 request authentication
- Host: GitHub
- URL: https://github.com/chimehq/oauthenticator
- Owner: ChimeHQ
- License: bsd-3-clause
- Created: 2021-06-16T15:22:48.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-11-13T18:39:15.000Z (4 days ago)
- Last Synced: 2024-11-13T19:34:46.884Z (4 days ago)
- Topics: oauth, oauth2, oauth2-client, swift
- Language: Swift
- Homepage:
- Size: 106 KB
- Stars: 46
- Watchers: 3
- Forks: 5
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
[![Build Status][build status badge]][build status]
[![Platforms][platforms badge]][platforms]
[![Documentation][documentation badge]][documentation]# OAuthenticator
Lightweight OAuth 2.0 request authentication in SwiftThere are lots of OAuth solutions out there. This one is small, uses Swift concurrency, and offers lots of control over the process.
Features:
- Swift concurrency support
- Fine-grained control over the entire token and refresh flow
- Optional integration with `ASWebAuthenticationSession`
- Control over when and if users are prompted to log into a serviceThere's also built-in support for services to streamline integration:
- GitHub
- Mastodon
- Google APIIf you'd like to contribute a similar thing for another service, please open a PR!
## Integration
Swift Package Manager:
```swift
dependencies: [
.package(url: "https://github.com/ChimeHQ/OAuthenticator", from: "0.3.0")
]
```## Usage
The main type is the `Authenticator`. It can execute a `URLRequest` in a similar fashion to `URLSession`, but will handle all authentication requirements and tack on the needed `Authorization` header. Its behavior is controlled via `Authenticator.Configuration` and `URLResponseProvider`. By default, the `URLResponseProvider` will be a private `URLSession`, but you can customize this if needed.
Setting up a `Configuration` can be more work, depending on the OAuth service you're interacting with.
```swift
// backing storage for your authentication data. Without this, tokens will be tied to the lifetime of the `Authenticator`.
let storage = LoginStorage {
// get login here
} storeLogin: { login in
// store `login` for later retrieval
}// application credentials for your OAuth service
let appCreds = AppCredentials(clientId: "client_id",
clientPassword: "client_secret",
scopes: [],
callbackURL: URL(string: "my://callback")!)// the user authentication function
let userAuthenticator = ASWebAuthenticationSession.userAuthenticator// functions that define how tokens are issued and refreshed
// This is the most complex bit, as all the pieces depend on exactly how the OAuth-based service works
let tokenHandling = TokenHandling(authorizationURLProvider: { appCreds in URL(string: "based on app credentials") }
loginProvider: { authURL, appCreds, codeURL, urlLoader in ... }
refreshProvider: { existingLogin, appCreds, urlLoader in ... },
responseStatusProvider: TokenHandling.refreshOrAuthorizeWhenUnauthorized)let config = Authenticator.Configuration(appCredentials: appCreds,
loginStorage: storage,
tokenHandling: tokenHandling,
userAuthenticator: userAuthenticator)let authenticator = Authenticator(config: config)
let myRequest = URLRequest(...)
let (data, response) = try await authenticator.response(for: myRequest)
```If you want to receive the result of the authentication process without issuing a URLRequest first, you can specify
an optional `Authenticator.AuthenticationStatusHandler` callback function within the `Authenticator.Configuration` initializer.This allows you to support special cases where you need to capture the `Login` object before executing your first
authenticated `URLRequest` and manage that separately.``` swift
let authenticationStatusHandler: Authenticator.AuthenticationStatusHandler = { result in
switch result {
case .success (let login):
authenticatedLogin = login
case .failure(let error):
print("Authentication failed: \(error)")
}
}// Configure Authenticator with result callback
let config = Authenticator.Configuration(appCredentials: appCreds,
tokenHandling: tokenHandling,
mode: .manualOnly,
userAuthenticator: userAuthenticator,
authenticationStatusHandler: authenticationStatusHandler)
let auth = Authenticator(config: config, urlLoader: mockLoader)
try await auth.authenticate()
if let authenticatedLogin = authenticatedLogin {
// Process special case
...
}
```### GitHub
OAuthenticator also comes with pre-packaged configuration for GitHub, which makes set up much more straight-forward.
```swift
// pre-configured for GitHub
let appCreds = AppCredentials(clientId: "client_id",
clientPassword: "client_secret",
scopes: [],
callbackURL: URL(string: "my://callback")!)let config = Authenticator.Configuration(appCredentials: appCreds,
tokenHandling: GitHub.tokenHandling())let authenticator = Authenticator(config: config)
let myRequest = URLRequest(...)
let (data, response) = try await authenticator.response(for: myRequest)
```### Mastodon
OAuthenticator also comes with pre-packaged configuration for Mastodon, which makes set up much more straight-forward.
For more info, please check out [https://docs.joinmastodon.org/client/token/](https://docs.joinmastodon.org/client/token/)```swift
// pre-configured for Mastodon
let userTokenParameters = Mastodon.UserTokenParameters(
host: "mastodon.social",
clientName: "MyMastodonApp",
redirectURI: "myMastodonApp://mastodon/oauth",
scopes: ["read", "write", "follow"]
)// The first thing we will need to do is to register an application, in order to be able to generate access tokens later.
// These values will be used to generate access tokens, so they should be cached for later use
let registrationData = try await Mastodon.register(with: userTokenParameters) { request in
try await URLSession.shared.data(for: request)
}// Now that we have an application, let’s obtain an access token that will authenticate our requests as that client application.
guard let redirectURI = registrationData.redirectURI, let callbackURL = URL(string: redirectURI) else {
throw AuthenticatorError.missingRedirectURI
}let appCreds = AppCredentials(
clientId: registrationData.clientID,
clientPassword: registrationData.clientSecret,
scopes: userTokenParameters.scopes,
callbackURL: callbackURL
)let config = Authenticator.Configuration(
appCredentials: appCreds,
tokenHandling: Mastodon.tokenHandling(with: userTokenParameters)
)let authenticator = Authenticator(config: config)
var urlBuilder = URLComponents()
urlBuilder.scheme = Mastodon.scheme
urlBuilder.host = userTokenParameters.hostguard let url = urlBuilder.url else {
throw AuthenticatorError.missingScheme
}let request = URLRequest(url: url)
let (data, response) = try await authenticator.response(for: request)
```### Google API
OAuthenticator also comes with pre-packaged configuration for Google APIs (access to Google Drive, Google People, Google Calendar, ...) according to the application requested scopes.More info about those at [Google Workspace](https://developers.google.com/workspace). The Google OAuth process is described in [Google Identity](https://developers.google.com/identity)
Integration example below:
```swift
// Configuration for Google API// Define how to store and retrieve the Google Access and Refresh Token
let storage = LoginStorage {
// Fetch token and return them as a Login object
return LoginFromSecureStorage(...)
} storeLogin: { login in
// Store access and refresh token in Secure storage
MySecureStorage(login: login)
}let appCreds = AppCredentials(clientId: googleClientApp.client_id,
clientPassword: googleClientApp.client_secret,
scopes: googleClientApp.scopes,
callbackURL: googleClient.callbackURL)let config = Authenticator.Configuration(appCredentials: Self.oceanCredentials,
loginStorage: storage,
tokenHandling: tokenHandling,
mode: .automatic)let authenticator = Authenticator(config: config)
// If you just want the user to authenticate his account and get the tokens, do 1:
// If you want to access a secure Google endpoint with the proper access token, do 2:// 1: Only Authenticate
try await authenticator.authenticate()// 2: Access secure Google endpoint (ie: Google Drive: upload a file) with access token
var urlBuilder = URLComponents()
urlBuilder.scheme = GoogleAPI.scheme // https:
urlBuilder.host = GoogleAPI.host // www.googleapis.com
urlBuilder.path = GoogleAPI.path // /upload/drive/v3/files
urlBuilder.queryItems = [
URLQueryItem(name: GoogleDrive.uploadType, value: "media"),
]guard let url = urlBuilder.url else {
throw AuthenticatorError.missingScheme
}let request = URLRequest(url: url)
request.httpMethod = "POST"
request.httpBody = ... // File data to uploadlet (data, response) = try await authenticator.response(for: request)
```## Contributing and Collaboration
I'd love to hear from you! Get in touch via an issue or pull request.
I prefer collaboration, and would love to find ways to work together if you have a similar project.
I prefer indentation with tabs for improved accessibility. But, I'd rather you use the system you want and make a PR than hesitate because of whitespace.
By participating in this project you agree to abide by the [Contributor Code of Conduct](CODE_OF_CONDUCT.md).
[build status]: https://github.com/ChimeHQ/OAuthenticator/actions
[build status badge]: https://github.com/ChimeHQ/OAuthenticator/workflows/CI/badge.svg
[platforms]: https://swiftpackageindex.com/ChimeHQ/OAuthenticator
[platforms badge]: https://img.shields.io/endpoint?url=https%3A%2F%2Fswiftpackageindex.com%2Fapi%2Fpackages%2FChimeHQ%2FOAuthenticator%2Fbadge%3Ftype%3Dplatforms
[documentation]: https://swiftpackageindex.com/ChimeHQ/OAuthenticator/main/documentation
[documentation badge]: https://img.shields.io/badge/Documentation-DocC-blue