oidcc
An OpenID Connect certified client library for Erlang and Elixir applications.
What is oidcc?
oidcc is an OpenID Connect client library for Erlang and Elixir that handles authentication and authorization flows. It solves the problem of securely integrating with identity providers by providing a certified, standards-compliant implementation of the OpenID Connect protocol.
Erlang and Elixir developers building applications that require secure user authentication via OpenID Connect, such as web services, APIs, or enterprise systems.
Developers choose oidcc for its OpenID Certification, comprehensive feature set covering modern protocol extensions, and its focus on security backed by a security audit, ensuring reliable and standards-compliant authentication.
Overview
OpenId Connect client library in Erlang & Elixir
Use Cases
Best For
- Adding OpenID Connect authentication to Erlang-based web services
- Securing Elixir Phoenix applications with standardized identity protocols
- Implementing FAPI 2.0 compliant financial-grade authentication
- Building microservices in Erlang/OTP that require token-based authorization
- Integrating with identity providers like Google, Auth0, or Okta in BEAM languages
- Developing applications needing advanced OpenID features like JARM or DPoP
Not Ideal For
- Projects requiring pre-built login UIs or frontend components
- Applications running on legacy Erlang/OTP versions below OTP26
- Teams that only need basic OAuth 2.0 without OpenID Connect's identity features
- Developers working in non-BEAM languages like JavaScript or Python
Pros & Cons
Pros
Certified for multiple Relaying Party conformance profiles, ensuring high interoperability with identity providers, as highlighted by the OpenID Connect Certified logo and conformance test suite link.
Implements advanced features like FAPI 2.0, JARM, DPoP, and PKCE, making it suitable for security-critical applications, with a detailed list in the Supported Features section.
Undergone a security audit by SAFE-Erlang-Elixir, adding credibility and trust for production use, as noted in the README with audit details.
Offers companion libraries for Cowboy, Plug, Phoenix, and Überauth, easing integration into common Erlang/Elixir web frameworks, mentioned in the Usage section.
Cons
Minimum supported OTP version is OTP26, excluding older systems and requiring upgrades, as explicitly stated in the Setup section.
Requires managing provider configuration workers and supervisor integration, which can be verbose and error-prone, as shown in the multi-step setup examples.
Tied exclusively to Erlang and Elixir, making it unusable for projects in other programming languages or ecosystems.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.