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
Please review these deprecations and important changes for Pomerium Enterprise before upgrading.
280
+
:::info
282
281
283
-
:::caution
282
+
Your Pomerium Enterprise version should always match the same **minor version number** as your Pomerium Core version. For example:
283
+
✅ Core **v0.27.0** with Enterprise **v0.27.3** is a supported configuration.
284
+
❌ Core **v0.27.0** with Enterprise **v0.28.0** is not supported.
284
285
285
-
<UpgradeNotice />
286
286
:::
287
287
288
+
To **upgrade** a Pomerium Enterprise deployment, we recommend that you:
289
+
290
+
1. Reach out to your account manager to let us know you are planning an upgrade, especially if upgrading across multiple minor versions at once.
291
+
1. First review the version-specific upgrade notes on this page for **both** Pomerium Core and Pomerium Enterprise for any changes that might pertain to your deployment. (If you're not sure, please don't hesitate to reach out and ask for clarification.)
292
+
1. Take a database backup of the Pomerium Enterprise database.
293
+
1. Upgrade Pomerium Core to the new version. For a replicated deployment, instances can be updated one at a time to avoid downtime.
294
+
1. Upgrade Pomerium Enterprise to the new version.
295
+
1. Verify that your deployment continues to behave as expected.
296
+
297
+
In case of trouble during the upgrade process, follow these steps to **roll back** to the previous version:
298
+
299
+
1. Stop Pomerium Enterprise.
300
+
1. Restore the Pomerium Enterprise database from a backup taken before the upgrade.
301
+
1. Downgrade Pomerium Core to the previous version.
302
+
1. Start the previous version of Pomerium Enterprise.
Bearer token format controls how HTTP bearer token authentication is handled.
6
+
keywords:
7
+
- reference
8
+
- Bearer Token Format
9
+
pagination_prev: null
10
+
pagination_next: null
11
+
toc_max_heading_level: 2
12
+
---
13
+
14
+
importTabsfrom'@theme/Tabs';
15
+
importTabItemfrom'@theme/TabItem';
16
+
17
+
# Bearer Token Format
18
+
19
+
## Summary
20
+
21
+
**Bearer Token Format** controls how HTTP bearer token authentication is handled. There are 3 possible options: `default`, `idp_access_token` and `idp_identity_token`.
22
+
23
+
HTTP bearer tokens are tokens stored in the `Authorization` header prefixed by `Bearer `:
24
+
25
+
```text
26
+
GET / HTTP/1.1
27
+
Authorization: Bearer Token
28
+
```
29
+
30
+
Pomerium's `default` behavior is to pass bearer tokens to upstream applications without interpreting them. Pomerium also supports creating sessions from tokens issued by an identity provider without needing to initiate an interactive login. If the `idp_access_token` option is used, then the bearer token will be interpreted as an IdP-issued access token. If the `idp_identity_token` option is used, then the bearer token will be interpreted as an IdP-issued identity token.
31
+
32
+
Currently only [Microsoft Entra](../integrations/user-identity/azure) is supported with this option.
33
+
34
+
This option can also be configured at the route-level.
35
+
36
+
## Additional Headers
37
+
38
+
Pomerium also always supports passing IdP access and identity tokens via the following headers (replacing `<TOKEN>` with the issued token):
IdP access token allowed audiences controls how the audience claim of an incoming IdP-issued access token is validated.
6
+
keywords:
7
+
- reference
8
+
- IdP Access Token Allowed Audiences
9
+
pagination_prev: null
10
+
pagination_next: null
11
+
toc_max_heading_level: 2
12
+
---
13
+
14
+
importTabsfrom'@theme/Tabs';
15
+
importTabItemfrom'@theme/TabItem';
16
+
17
+
# IdP Access Token Allowed Audiences
18
+
19
+
## Summary
20
+
21
+
**IdP Access Token Allowed Audiences** controls how the audience claim of an incoming IdP-issued access token is validated.
22
+
23
+
For [Microsoft Entra](../integrations/user-identity/azure) an access-token is a JWT with an audience claim. When the IdP Access Token Allowed Audiences option is set, the `aud` claim of the access token JWT must match one of the entries.
24
+
25
+
This option can also be configured at the route-level.
0 commit comments