This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
commit 836b55ef78dd46acb39aea55503407354a62f125
Author: Jacques Le Roux <jacques.le.r...@les7arts.com>
AuthorDate: Thu Feb 8 11:21:59 2024 +0100
Fixed: Fix trunk documentation generation in BuidBot (OFBIZ-12896)
It's a weird mess, maybe I miss something :/
Some same includes links that works well in 18.12 branch don't in trunk. I
thought it could be due to java version but not even since I see that in the
18.12 build:
To honour the JVM settings for this build a new JVM will be forked.
> Task :deleteOfbizDocumentation
> Task :generateOfbizDocumentation
unsupported Java version "11", defaulting to 1.7
BUILD SUCCESSFUL in 55s
2 actionable tasks: 2 executed
---
.../webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
a/framework/webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc
b/framework/webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc
index b5d76ea7f1..77361b1f4d 100644
--- a/framework/webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc
+++ b/framework/webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc
@@ -23,8 +23,8 @@ under the License.
As more explained at bottom of
https://issues.apache.org/jira/browse/OFBIZ-11594, the introduction of "the
SameSite attribute set to 'strict' for all cookies"
with https://issues.apache.org/jira/browse/OFBIZ-11470 prevents the internal
Single Sign On feature.
-There are ways to make it available as explained at bottom of
https://issues.apache.org/jira/browse/OFBIZ-11594. It's not implemented OOTB
-
+There are ways to make it available as explained at bottom of
https://issues.apache.org/jira/browse/OFBIZ-11594.
+It's not implemented OOTB
====
@@ -68,6 +68,8 @@ webappName.securedLoginId cookie, creates a JWT containing
the userLoginId, and
. Then the sendJWT() Ajax function sends an Authorization header containing
the JWT to the URL to reach.
At this stage, if all things are correct, the flow leaves the source side.
+. *Last but not least*. To make this work you have to set the
security.internal.sso.enabled and security.token.key SystemProperty entities
locally and on trunk demo server
+
.On the server side:
. A CORS policy is needed. _Without it, the Authorization token containing the
JWT will be rejected.
It's a simple policy but you need to strictly define the authorized domains.
Never use the lazy "*" for domains
