Current section
Files
Jump to
Current section
Files
ueberauth_bexio
README.md
README.md
# Überauth Bexio
[](https://github.com/titaniumcoder/ueberauth_bexio/actions/workflows/elixir.yml)
[](https://hex.pm/packages/ueberauth_bexio)
[](https://hexdocs.pm/ueberauth_bexio/)
[](https://hex.pm/packages/ueberauth_bexio)
[](https://github.com/titaniumcoder/ueberauth_bexio/blob/main/LICENSE)
[](https://github.com/titaniumcoder/ueberauth_bexio/commits/main)
> Bexio OAuth2 strategy for Überauth.
## Installation
1. Setup your application at [Bexio Developer](https://developer.bexio.com/).
2. Add `:ueberauth_bexio` to your list of dependencies in `mix.exs`:
```elixir
def deps do
[
{:ueberauth_bexio, "~> 0.5.0"}
]
end
```
3. Add Bexio to your Überauth configuration:
```elixir
config :ueberauth, Ueberauth,
providers: [
bexio: {Ueberauth.Strategy.Bexio, []}
]
```
4. Update your provider configuration:
Use that if you want to read client ID/secret from the environment
variables in the compile time:
```elixir
config :ueberauth, Ueberauth.Strategy.Bexio.OAuth,
client_id: System.get_env("BEXIO_CLIENT_ID"),
client_secret: System.get_env("BEXIO_CLIENT_SECRET")
```
Use that if you want to read client ID/secret from the environment
variables in the run time:
```elixir
config :ueberauth, Ueberauth.Strategy.Bexio.OAuth,
client_id: {System, :get_env, ["BEXIO_CLIENT_ID"]},
client_secret: {System, :get_env, ["BEXIO_CLIENT_SECRET"]}
```
5. Include the Überauth plug in your controller:
```elixir
defmodule MyApp.AuthController do
use MyApp.Web, :controller
plug Ueberauth
...
end
```
6. Create the request and callback routes if you haven't already:
```elixir
scope "/auth", MyApp do
pipe_through :browser
get "/:provider", AuthController, :request
get "/:provider/callback", AuthController, :callback
end
```
7. Your controller needs to implement callbacks to deal with `Ueberauth.Auth` and `Ueberauth.Failure` responses.
For an example implementation see the [Überauth Example](https://github.com/ueberauth/ueberauth_example) application.
## Calling
Depending on the configured url you can initiate the request through:
/auth/bexio
Or with options:
/auth/bexio?scope=email%20profile
By default the requested scope is "email profile openid". Scope can be configured either explicitly as a `scope` query value on the request path or in your configuration:
```elixir
config :ueberauth, Ueberauth,
providers: [
bexio: {Ueberauth.Strategy.Bexio, [default_scope: "openid email profile company_profile"]}
]
```
To guard against client-side request modification, it's important to still check the domain in `info.urls[:website]` within the `Ueberauth.Auth` struct if you want to limit sign-in to a specific domain.
## Single logout
The strategy builds the Keycloak/OIDC end-session (RP-initiated logout) URL from the `"end_session_endpoint"` published in the Bexio realm's OpenID Connect discovery document:
```elixir
Ueberauth.Strategy.Bexio.logout_url()
#=> "https://auth.bexio.com/realms/bexio/protocol/openid-connect/logout"
```
It accepts optional `:client_id`, `:post_logout_redirect_uri`, and `:id_token_hint` options and returns the full URL with the query params encoded.
Reading the URL requires a request to the discovery document — cache the result in your application if you log out frequently. If the provider does not publish an `"end_session_endpoint"` (or discovery fails), `logout_url/1` returns `nil`; handle that by only clearing your local session.
Use it in your log-out action: clear the local session first, then redirect the user to the end-session endpoint:
```elixir
def delete(conn, _params) do
case Ueberauth.Strategy.Bexio.logout_url(
client_id: "my_client",
post_logout_redirect_uri: "https://myapp.example.com/logged_out",
id_token_hint: id_token
) do
nil ->
# Single logout not available — only clear the local session
conn
|> configure_session(drop: true)
|> clear_session()
|> redirect(to: "/")
logout_url ->
conn
|> configure_session(drop: true)
|> clear_session()
|> redirect(external: logout_url)
end
end
```
If you use `:post_logout_redirect_uri`, the URI must be registered as an allowed post-logout redirect for your application in the [Bexio developer portal](https://developer.bexio.com/); otherwise Bexio will reject the logout request.
## Copyright and License
Copyright (c) 2026 Rico Metzger
Released under the MIT License, which can be found in the repository in [LICENSE](https://github.com/titaniumcoder/ueberauth_bexio/blob/main/LICENSE).