# Leptos OIDC Authentication
**leptos_oidc** is a utility library for handling OpenID Connect (OIDC)
authentication within the Leptos framework. It simplifies the integration of
OIDC authentication flows with Leptos-based applications, making it easier to
manage user authentication and tokens.
## Table of Contents
- [Leptos compatibility](leptos-compatibility)
- [Features](#features)
- [Missing Features](#missing-features)
- [Tested Backends with Example](#tested-backends-with-example)
- [Usage](#usage)
- [Initialization](#initialization)
- [Generating Login and Logout URLs](#generating-login-and-logout-urls)
- [Conditional Rendering Components](#conditional-rendering-components)
- [Refreshing Access Tokens](#refreshing-access-tokens)
- [License](#license)
## Leptos compatibility
| Crate version | Compatible Leptos version |
|---------------|---------------------------|
| <= 0.3 | 0.5 |
| 0.4-0.7 | 0.6 |
## Features
**leptos_oidc** offers the following features:
- Initialization of the OIDC authentication process.
- Generation of login and logout URLs for redirecting users to OIDC providers (e.g., Keycloak).
- Conditional rendering of components based on the authentication state.
- Refreshing access tokens and storing them in local storage.
- Working with client and server side rendering
- Automatically refresh the access token in the background.
- PKCE challenge
### Missing Features
- Make refresh token optional
- Some minor code refactoring/cleanup
### Tested Backends with Example
**leptos_oidc** was tested with various backends. This doesn't mean that other
backends are not supported. Every backend which is support `oidc` should work.
But feel free to ask for advice or give feedback!
Tested backends:
- [KeyCloak](https://github.com/keycloak/keycloak)
- [rauthy](https://github.com/sebadob/rauthy/)
You can find a setup guide for the backends under [docs/backends](docs/backends/README.md).
#### Keycloak
#### Rauthy
## Installation
To use **leptos_oidc** in your Leptos-based application, add it as a dependency
in your `Cargo.toml` file:
```toml
[dependencies]
leptos_oidc = "0.7"
```
Note: This needs at least `leptos v0.6`.
## Usage
### Initialization and Example
To get started with OIDC authentication, initialize the library with the
required authentication parameters. You can use the `AuthParameters` struct
to specify the OIDC endpoints, client ID, redirect URIs, and other relevant
information.
Please keep in mind that the `issuer` url needs to be the base url without the `/.well-known/openid-configuration`.
```rust
use leptos::*;
use leptos_oidc::{Auth, AuthParameters};
#[component]
pub fn App() -> impl IntoView {
provide_meta_context();
view! {
}
}
#[component]
pub fn AppWithRouter() -> impl IntoView {
// Specify OIDC authentication parameters here.
// Note: This is an example for keycloak, please change it to your needs
let auth_parameters = AuthParameters {
issuer: "https://ENDPOINT/auth/v1".to_string(),
client_id: "CLIENT_ID".to_string(),
redirect_uri: "http://localhost:3000/profile".to_string(),
post_logout_redirect_uri: "http://localhost:3000/bye".to_string(),
challenge: Challenge::S256,
scope: Some("openid%20profile%20email"),
audience: None,
};
let auth = Auth::init(auth_parameters);
view! {
// This is an example for a navbar where you have a login and logout
// button, based on the state.
Sign in
}
}>
Sign Out
}/>
// This is an example route for your profile, it will render
// loading if it's still loading, render unauthenticated if it's
// unauthenticated and it will render the children, if it's
// authenticated
}
unauthenticated=move || view! { }
>
}
}
/>
}
}
#[component]
pub fn Home() -> impl IntoView {
let auth = expect_context::();
view! {
Home
// Your Pome Page without authentication
}
}
/// This will be rendered, if the authentication library is still loading
#[component]
pub fn Loading() -> impl IntoView {
view! {
Loading
// Your Loading Page/Animation
}
}
/// This will be rendered, if the user is unauthenticated
#[component]
pub fn Unauthenticated() -> impl IntoView {
view! {
Unauthenticated
// Your Unauthenticated Page
}
}
/// This will be rendered, if the user is authentication
#[component]
pub fn Profile() -> impl IntoView {
view! {
Profile
// Your Profile Page
}
}
```
Note: Please keep in mind that the `Auth::init` needs to be `inside a Router`.
The internal state is using `use_query`, which is only available inside a
`Router`.
### Generating Login and Logout URLs
**leptos_oidc** provides functions to generate login and logout URLs for your
application. These URLs are used to redirect users to the OIDC provider for
authentication and logout.
```rust
use leptos::*;
use leptos_oidc::Auth;
#[component]
fn MyComponent() {
let auth = expect_context::();
// Generate the login URL to initiate the authentication process.
let login_url = move || auth.login_url();
// Generate the logout URL for logging out the user.
let logout_url = move || auth.logout_url();
}
```
### Conditional Rendering Components
The library includes transparent components to conditionally render content
based on the authentication state. These components simplify the user interface
when dealing with authenticated and unauthenticated users.
```rust
use leptos::*;
use leptos_oidc::Auth;
#[component]
fn MyComponent() {
view! {
// Generate Sign In link
Sign in
// Generate Sign Out link
Sign Out"This will be rendered only when the auth library is not loading anymore""This will be rendered only when the auth library is still loading""This will only be rendered if the user is authenticated"
// A more complex example with optional fallbacks for the loading and unauthenticated state
"This will only be rendered if the user is authenticated"
}
}
```
### Refreshing Access Tokens
This library is now capable of refreshing the `access_token` in the background. :)
## License
**leptos_oidc** is distributed under the [MIT License](https://opensource.org/licenses/MIT).
For more information, see the [LICENSE](https://gitlab.com/kerkmann/leptos_oidc/blob/main/LICENSE) file.