website: bump prettier from 3.5.3 to 3.6.0 in /website (#15199)
* website: bump prettier from 3.5.3 to 3.6.0 in /website Bumps [prettier](https://github.com/prettier/prettier) from 3.5.3 to 3.6.0. - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](https://github.com/prettier/prettier/compare/3.5.3...3.6.0) --- updated-dependencies: - dependency-name: prettier dependency-version: 3.6.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * format Signed-off-by: Jens Langhammer <jens@goauthentik.io> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Jens Langhammer <jens@goauthentik.io> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
dependabot[bot]
@ -14,7 +14,6 @@ slug: "/releases/2021.2"
|
||||
- Improved support for different LDAP Servers
|
||||
|
||||
The LDAP source has improved support for non-Active Directory LDAP setups. This includes the following changes:
|
||||
|
||||
- Switch to sync membership from groups to users rather than user to group
|
||||
- Fix users, which were removed from a group in LDAP not being removed from said group
|
||||
- Add support for LDAP servers which have core fields declared as lists
|
||||
|
||||
@ -11,7 +11,6 @@ slug: "/releases/2021.4"
|
||||
You can now configure if _all_ policies need to pass, or if _any_ policy needs to pass.
|
||||
|
||||
This can now be configured for the following objects:
|
||||
|
||||
- Applications (access restrictions)
|
||||
- Sources
|
||||
- Flows
|
||||
@ -27,7 +26,6 @@ slug: "/releases/2021.4"
|
||||
- New UI
|
||||
|
||||
While the UI mostly looks the same, under the hood a lot has changed. The Web UI is now a Single-page application based on rollup and lit-html. This has several consequences and new features, for example:
|
||||
|
||||
- You can now see a user's OAuth Access/Refresh tokens and the consents they've given
|
||||
- You can now see a per-object changelog based on the model_create/update/delete events being created.
|
||||
- A new API Browser is available under `https://authentink.company/api/v2beta/`
|
||||
|
||||
@ -41,7 +41,6 @@ This feature is still in technical preview, so please report any Bugs you run in
|
||||
You can now configure how a source behaves after the user has authenticated themselves to the source. Previously, authentik always checked the unique identifier from the source, enrolled the user when the identifier didn't exist and authenticated the user otherwise.
|
||||
|
||||
Now you can configure how the matching should be done:
|
||||
|
||||
- Identifier: Keeps the old behaviour, can lead to duplicate user accounts
|
||||
- Email (link): If a user with the same Email address exists, they are linked. Can have security implications when a source doesn't validate email addresses.
|
||||
- Email (deny): Deny the flow if the Email address is already used.
|
||||
|
||||
@ -16,7 +16,6 @@ slug: "/releases/2021.6"
|
||||
This version adds soft multi-tenancy. This means you can configure different branding settings and different default flows per domain.
|
||||
|
||||
This also changes how a default flow is determined. Previously, for defaults flow, authentik would pick the first flow that
|
||||
|
||||
- matches the required designation
|
||||
- comes first sorted by slug
|
||||
- is allowed by policies
|
||||
|
||||
Reference in New Issue
Block a user