saschazegerman / loginbuddy

A generic web application handling login flows via OpenID Connect

About Loginbuddy

Latest update: January 2024! See what has changed here: WIKI

Loginbuddy is a container based solution that handles OpenID Connect flows and is used as proxy between an application (your application) and an OpenID Provider (OP). Your application only needs to communicate with Loginbuddy. After finishing the authentication and authorization flow with providers, Loginbuddy generates a single response through a stable, normalized, interface to the application.

The high level design looks like this:

Getting started

To get started, checkout the samples project.

Loginbuddy includes configuration templates for common OpenID providers which simplifies the configuration effort:

• Google
• GitHub
• LinkedIn
• Sign In with Apple
• PingOne (Ping Identity)
• Amazon (Login with Amazon)
• OpenID Dynamic registration
• Spotify
• self-issued

API and Protocols

Loginbuddy is built to support OpenID Connect and OAuth 2.0 specifications:

• OAuth 2.0
• OpenID Connect Core
• OpenID Connect Discovery
• OpenID Connect Dynamic Registration
• OAuth 2.0 Pushed Authorization Requests

For more details on the APIs supported see WIKI - Protocols and APIs.

Other Resources

To get a better idea how it works I have published a few videos about Loginbuddy on YouTube: Loginbuddy playlist

WIKI

All documentation for Loginbuddy can be found in the local WIKI

License

Copyright (c) 2024. All rights reserved.

This software may be modified and distributed under the terms of the Apache License 2.0 license. See the LICENSE file for details.

loginbuddy's Issues

Multiple references to templates cause NullPointException

If multiple provider configurations in 'config.json' reference templates Loginbuddy ends with a NullPointerException.
The expectation is that any number of references to templates should be supported