An easy-to-use OAuth 2.0 client library for iOS, written in Swift, supporting password grant and token refresh.
Heimdallr is an OAuth 2.0 client library for iOS, written in Swift, that simplifies implementing authentication flows in mobile applications. It handles token requests, persistence, and automatic refresh, allowing developers to integrate OAuth 2.0 with minimal boilerplate code. The library specifically supports the resource owner password credentials grant, extension grants, and token refreshing as per the OAuth 2.0 specification.
iOS developers building apps that require OAuth 2.0 authentication, particularly those using the password grant flow or needing secure token management. It is suited for teams looking for a lightweight, Swift-native solution.
Developers choose Heimdallr for its straightforward API, built-in secure token storage via Keychain, and automatic token refresh capabilities. It reduces the complexity of OAuth 2.0 integration while providing flexibility through configurable components like HTTP clients and token parsers.
Easy to use OAuth 2 library for iOS, written in Swift.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers a straightforward interface for OAuth 2.0 operations, as shown in the README's simple examples for token requests and URLRequest authentication, reducing boilerplate code.
Includes built-in OAuthAccessTokenKeychainStore that persists access tokens securely in the iOS Keychain, providing out-of-the-box security without extra setup.
Handles refreshing expired access tokens automatically when a refresh token is available, simplifying session management and adhering to OAuth 2.0 specifications.
Allows customization via protocols for HTTP clients, token parsers, and request authenticators, offering flexibility for specific server requirements or advanced use cases.
The README explicitly states the repository is no longer actively maintained, posing significant risks for security vulnerabilities, compatibility with new iOS versions, and lack of bug fixes.
Primarily supports only the resource owner password credentials grant and extension grants, missing native implementations for common flows like authorization code grant, which is essential for many OAuth providers.
As an unmaintained project, it lacks community-driven extensions, tutorials, or third-party integrations compared to active alternatives, making troubleshooting and advanced usage difficult.
Without updates, it may not adapt to Swift language evolution or changes in OAuth standards, leading to integration issues or deprecation warnings in future Xcode versions.