You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ofbiz.apache.org by jl...@apache.org on 2024/02/08 11:03:10 UTC

(ofbiz-framework) branch trunk updated (cd67b3e5ab -> 836b55ef78)

This is an automated email from the ASF dual-hosted git repository.

jleroux pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git


    from cd67b3e5ab Improved: Add logging to docker host filesystem in example docker compose configuration (OFBIZ-12889)
     new 7f2e61c14a Fixed: sonarcloud.io no longer exists, hence no project_badges for OFBiz
     new 836b55ef78 Fixed: Fix trunk documentation generation in BuidBot (OFBIZ-12896)

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 README.adoc                                                         | 3 +--
 .../webapp/src/docs/asciidoc/_include/wa-cross-domains-SSO.adoc     | 6 ++++--
 2 files changed, 5 insertions(+), 4 deletions(-)


(ofbiz-framework) 01/02: Fixed: sonarcloud.io no longer exists, hence no project_badges for OFBiz

Posted by jl...@apache.org.
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 7f2e61c14af16004505524f8b74c17a0c321c889
Author: Jacques Le Roux <ja...@les7arts.com>
AuthorDate: Thu Feb 8 10:54:27 2024 +0100

    Fixed: sonarcloud.io no longer exists, hence no project_badges for OFBiz
    
    It seems complicated to find a solution, for such a cosmetic thing anyway.
    
    Also fixes a "duplicated" URL
---
 README.adoc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.adoc b/README.adoc
index ca6cbd9f2b..772568b08b 100644
--- a/README.adoc
+++ b/README.adoc
@@ -24,7 +24,6 @@ image:https://img.shields.io/badge/License-Apache%202.0-blue.svg[link=http://www
 image:https://img.shields.io/badge/Version-trunk-blue.svg[link=https://github.com/apache/ofbiz-framework]
 image:https://ci2.apache.org/badges/ofbizTrunkFrameworkPlugins.svg[link=https://ci2.apache.org/#/builders?tags=%2BofbizTrunkFrameworkPlugins]
 image:https://github.com/apache/ofbiz-framework/actions/workflows/gradle.yaml/badge.svg?branch=trunk[link=https://github.com/apache/ofbiz-framework/actions/workflows/gradle.yaml]
-image:https://sonarcloud.io/api/project_badges/measure?project=apache_ofbiz-framework&metric=alert_status[link=https://sonarcloud.io/dashboard?id=apache_ofbiz-framework]
 image:https://qpkb254zxeu.montastic.io/badge[link=https://qpkb254zxeu.montastic.io]
 //image:https://github.com/apache/ofbiz-framework/actions/workflows/codeql-analysis.yml/badge.svg[link=https://github.com/apache/ofbiz-framework/actions/workflows/codeql-analysis.yml]
 
@@ -104,7 +103,7 @@ ____
 "Powershell is not recognized as an internal or external command, operable program or batch file"
 ____
 
-follow the advice there: https://s.apache.org/vdcv8. If you want more details see: https://s.apache.org/ac7no
+follow the advice there: https://s.apache.org/vdcv8. If you want more details see: https://s.apache.org/urnju
 
 * If you run into problems check the the execution policy of PowerShell. See https://s.apache.org/urnju for details.
 By setting the execution policy to "unrestricted", you'll be prompted to run the script once you run the init-gradle-wrapper command.


(ofbiz-framework) 02/02: Fixed: Fix trunk documentation generation in BuidBot (OFBIZ-12896)

Posted by jl...@apache.org.
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 <ja...@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