You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/how-to/authenticate.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,8 @@
1
-
# Authenticate to BlueAPI
1
+
> [!NOTE]
2
+
> If you are using `oauth2-proxy` to secure the Swagger UI documentation page, you can log out by visiting the `/logout` URL. For this to work correctly, ensure that the blueapi server is configured with
3
+
> `oidc.logout_redirect_endpoint` set to `/oauth2/sign_out`, which is required for `oauth2-proxy`.
4
+
5
+
# Authenticate to BlueAPI-Cli
2
6
3
7
## Introduction
4
8
BlueAPI provides a secure and efficient way to interact with its services. This guide walks you through the steps to log in and log out using BlueAPI with OpenID Connect (OIDC) authentication.
@@ -63,9 +67,3 @@ To log out and securely remove the cached access token, follow these steps:
63
67
```
64
68
Logged out
65
69
```
66
-
67
-
68
-
> [!NOTE]
69
-
> The login and logout instructions above apply to the CLI. If you are using `oauth2-proxy` to secure the Swagger
70
-
> UI documentation page, you can log out by visiting the `/logout` URL. For other OIDC providers, update the
71
-
> `oidc.logout_redirect_endpoint` configuration to the appropriate logout endpoint.
0 commit comments