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

KEYCLOAK-15428 Fix two broken links causing test failures

Browse source 
http://browsercookielimits.squawky.net no longer exists, and I can't find an
equivilent of what it did, so I've removed it.

https://wildfly.org needed a slash on the end and a www up front, to prevent a redirect.

That should resolve the test failures currently causing all PRs to be flagged.
This commit is contained in:
Alex Szczuczko 2020-09-02 07:02:46 -06:00 committed by Bruno Oliveira da Silva
parent afb6e99e3c
commit 106669cd45
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
getting_started/topics/sample-app/proc-adjusting-ports.adoc
View file

@ -15,7 +15,7 @@ To avoid port conflicts, you need different ports to run {project_name} and {app
.Procedure
ifeval::[{project_community}==true]
. Download WildFly from link:https://wildfly.org[WildFly.org].
. Download WildFly from link:https://www.wildfly.org/[WildFly.org].
endif::[]
ifeval::[{project_product}==true]
. Download JBoss EAP 7.3 from the https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=appplatform&downloadType=distributions[Red Hat customer portal].
@ -49,4 +49,4 @@ $ ./standalone.sh -Djboss.socket.binding.port-offset=100
. Confirm that the {project_name} server is running. Go to http://localhost:8180/auth/admin/ .
+
If the admin console opens, you are ready to install a client adapter that enables {appserver_name} to work with {project_name}.
If the admin console opens, you are ready to install a client adapter that enables {appserver_name} to work with {project_name}.

2
securing_apps/topics/oidc/keycloak-gatekeeper.adoc
View file

@ -513,7 +513,7 @@ Assuming `--enable-metrics` has been set, a Prometheus endpoint can be found on
==== Limitations
Keep in mind link:http://browsercookielimits.squawky.net/[browser cookie limits] if you use access or refresh tokens in the browser cookie. Keycloak-generic-adapter divides the cookie automatically if your cookie is longer than 4093 bytes. Real size of the cookie depends on the content of the issued access token. Also, encryption might add additional bytes to the cookie size. If you have large cookies (>200 KB), you might reach browser cookie limits.
Keep in mind browser cookie limits if you use access or refresh tokens in the browser cookie. Keycloak-generic-adapter divides the cookie automatically if your cookie is longer than 4093 bytes. Real size of the cookie depends on the content of the issued access token. Also, encryption might add additional bytes to the cookie size. If you have large cookies (>200 KB), you might reach browser cookie limits.
All cookies are part of the header request, so you might find a problem with the max headers size limits in your infrastructure (some load balancers have very low this value, such as 8 KB). Be sure that all network devices have sufficient header size limits. Otherwise, your users won't be able to obtain an access token.