libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

Fixing downstream documentation build (#27781)

Browse source 
Closes #27780

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
Alexander Schwartz 2024-03-12 08:37:41 +01:00 committed by GitHub
parent 1c0c56e805
commit 967ceddfbb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/documentation/tests/src/test/resources/ignored-links
View file

@ -44,3 +44,4 @@ https://github.com/keycloak/keycloak/blob/025778fe9c745316f80b53fe3052aeb314e868
https://github.com/keycloak/keycloak/issues/new?* https://github.com/keycloak/keycloak/issues/new?*
https://stackapps.com/apps/oauth/register https://stackapps.com/apps/oauth/register
https://github.com/keycloak/keycloak-quickstarts/tree/release/24.0/extension/extend-account-console https://github.com/keycloak/keycloak-quickstarts/tree/release/24.0/extension/extend-account-console
https://github.com/keycloak/keycloak/releases/download/DEV/keycloak-DEV.zip

10
docs/documentation/upgrading/topics/changes/changes-23_0_0.adoc
View file

@ -14,12 +14,12 @@ which can be turned on to prevent adding the `iss` parameter to the authenticati
= Wildcard characters handling = Wildcard characters handling
JPA allows wildcards `%` and `_` when searching, while other providers like LDAP allow only `*`. JPA allows wildcards `%` and `+_+` when searching, while other providers like LDAP allow only `+*+`.
As `*` is a natural wildcard character in LDAP, it works in all places, while with JPA it only As `+*+` is a natural wildcard character in LDAP, it works in all places, while with JPA it only
worked at the beginning and the end of the search string. Starting with this release the only worked at the beginning and the end of the search string. Starting with this release the only
wildcard character is `*` which work consistently across all providers in all places in the search wildcard character is `+*+` which work consistently across all providers in all places in the search
string. All special characters in a specific provider like `%` and `_` for JPA are escaped. For exact string. All special characters in a specific provider like `%` and `+_+` for JPA are escaped. For exact
search, with added quotes e.g. `"w*ord"`, the behavior remains the same as in previous releases. search, with added quotes e.g. `+"w*ord"+`, the behavior remains the same as in previous releases.
= Language files for themes default to UTF-8 encoding = Language files for themes default to UTF-8 encoding

2
docs/documentation/upgrading/topics/changes/changes-24_0_0.adoc
View file

@ -179,7 +179,7 @@ to the new template.
= Truststore Changes = Truststore Changes
The `spi-truststore-file-*` options and the truststore related options `https-trust-store-*` are deprecated. Therefore, use the new default location for truststore material, `conf/truststores`, or specify your desired paths by using the `truststore-paths` option. For details, see the relevant https://www.keycloak.org/server/keycloak-truststore[guide]. The `+spi-truststore-file-*+` options and the truststore related options `+https-trust-store-*+` are deprecated. Therefore, use the new default location for truststore material, `conf/truststores`, or specify your desired paths by using the `truststore-paths` option. For details, see the relevant https://www.keycloak.org/server/keycloak-truststore[guide].
The `tls-hostname-verifier` property should be used instead of the `spi-truststore-file-hostname-verification-policy` property. The `tls-hostname-verifier` property should be used instead of the `spi-truststore-file-hostname-verification-policy` property.

1
docs/documentation/upgrading/topics/changes/changes.adoc
View file

@ -1,3 +1,4 @@
[[migration-changes]]
== Migration Changes == Migration Changes
=== Migrating to 25.0.0 === Migrating to 25.0.0