Worklytics
diff --git a/‎.github/workflows/build-java.yaml‎
Lines changed: 10 additions & 0 deletions b/‎.github/workflows/build-java.yaml‎
Lines changed: 10 additions & 0 deletions
diff --git a/‎.github/workflows/ci-java-all.yaml‎
Lines changed: 6 additions & 7 deletions b/‎.github/workflows/ci-java-all.yaml‎
Lines changed: 6 additions & 7 deletions
diff --git a/‎README.md‎
Lines changed: 10 additions & 24 deletions b/‎README.md‎
Lines changed: 10 additions & 24 deletions
diff --git a/‎docs/README.md‎
Lines changed: 9 additions & 14 deletions b/‎docs/README.md‎
Lines changed: 9 additions & 14 deletions
@@ -16,6 +16,11 @@ on:
         type: string
         description: java distribution to use # see https://github.com/actions/setup-java#supported-distributions
         default: corretto
+      maven-version:
+        required: false
+        type: string
+        description: maven version to use # see https://github.com/s4u/setup-maven-action#supported-version-syntax
+        default: '3.9.10' # 3.9.10+ is required for Java 24; in theory, we support earlier shoudl we test?
 
 jobs:
   ci_java:
@@ -29,6 +34,11 @@ jobs:
           java-version: ${{ inputs.java-version }}
           # https://github.com/actions/setup-java#supported-distributions
           distribution: ${{ inputs.java-distribution }}
+      - name: Setup Maven Action
+        uses: s4u/[email protected]
+        with:
+          java-version: ${{ inputs.java-version }}
+          maven-version: ${{ inputs.maven-version }}
       - name: Cache Maven packages
         uses: actions/cache@v3
         with:
 
@@ -19,6 +19,7 @@ jobs:
     uses: ./.github/workflows/build-java.yaml
     with:
       java-version: '17'
+      maven-version: '3.6.3' # just for interests sake
 
   # Java 21 - released 19 Sept 2023, supported until Sept 2028 (LTS)
   ci_java21:
@@ -32,10 +33,8 @@ jobs:
     with:
       java-version: '23'
 
-# Java 24 disabled, pending Maven releasing 3.9.10 or 4.x version that supports Java 24
-# specific issue is https://issues.apache.org/jira/browse/MNG-8248
-#  # Java 24 - released 18 March 2025, supported until Sept 2025
-#  ci_java24:
-#    uses: ./.github/workflows/build-java.yaml
-#    with:
-#      java-version: '24'
+ # Java 24 - released 18 March 2025, supported until Sept 2025
+ ci_java24:
+   uses: ./.github/workflows/build-java.yaml
+   with:
+     java-version: '24'
@@ -6,31 +6,18 @@
 
 A serverless, pseudonymizing, DLP layer between Worklytics and the REST API of your data sources.
 
-Psoxy replaces PII in your organization's data with hash tokens to enable Worklytics's analysis to
-be performed on anonymized data which we cannot map back to any identifiable individual.
+Psoxy replaces PII in your organization's data with hash tokens to enable Worklytics's analysis to be performed on anonymized data which we cannot map back to any identifiable individual.
 
-Psoxy is a pseudonymization service that acts as a Security / Compliance layer, which you can deploy
-between your data sources (SaaS tool APIs, Cloud storage buckets, etc) and the tools that need to
-access those sources.
+Psoxy is a pseudonymization service that acts as a Security / Compliance layer, which you can deploy between your data sources (SaaS tool APIs, Cloud storage buckets, etc) and the tools that need to access those sources.
 
-Psoxy ensures more secure, granular data access than direct connections between your tools will
-offer - and enforces access rules to fulfill your Compliance requirements.
+Psoxy ensures more secure, granular data access than direct connections between your tools will offer - and enforces access rules to fulfill your Compliance requirements.
 
-Psoxy functions as API-level Data Loss Prevention layer (DLP), by blocking sensitive fields / values
-/ endpoints that would otherwise be exposed when you connect a data sources API to a 3rd party
-service. It can ensure that data which would otherwise be exposed to a 3rd party service, due to
-granularity of source API models/permissions, is not accessed or transfered to the service.
+Psoxy functions as API-level Data Loss Prevention layer (DLP), by blocking sensitive fields / values / endpoints that would otherwise be exposed when you connect a data sources API to a 3rd party service. It can ensure that data which would otherwise be exposed to a 3rd party service, due to granularity of source API models/permissions, is not accessed or transferred to the service.
 
 Objectives:
-  - **serverless** - we strive to minimize the moving pieces required to run psoxy at scale, keeping
-     your attack surface small and operational complexity low. Furthermore, we define
-     infrastructure-as-code to ease setup.
-  - **transparent** - psoxy's source code is available to customers, to facilitate code review
-     and white box penetration testing.
-  - **simple** - psoxy's functionality will focus on performing secure authentication with the 3rd
-     party API and then perform minimal transformation on the response (pseudonymization, field
-     redaction) to ease code review and auditing of its behavior.
-
+  - **serverless** - we strive to minimize the moving pieces required to run psoxy at scale, keeping your attack surface small and operational complexity low. Furthermore, we define infrastructure-as-code to ease setup.
+  - **transparent** - psoxy's source code is available to customers, to facilitate code review and white box penetration testing.
+  - **simple** - psoxy's functionality will focus on performing secure authentication with the 3rd party API and then perform minimal transformation on the response (pseudonymization, field redaction) to ease code review and auditing of its behavior.
 
 ## Documentation
 
@@ -40,7 +27,6 @@ For development purposes, latest docs are also accessible at GitHub [docs/](./do
 
 ## Support
 
-Psoxy is maintained by Worklytics, Co. Support as well as professional services to assist with
-configuration and customization are available. Please contact
-[[email protected]](mailto:[email protected]) for more information or visit
-[www.worklytics.co](https://www.worklytics.co).
+Psoxy is maintained by Worklytics, Co.
+
+Support, as well as professional services, to assist with configuration and customization are available. Please contact [[email protected]](mailto:[email protected]) for more information or visit [www.worklytics.co](https://www.worklytics.co).
@@ -47,26 +47,22 @@ But Psoxy ensures Worklytics only sees:
 }
 ```
 
-These pseudonyms leverage SHA-256 hashing / AES encryption, with salt/keys that are known only to
-your organization and never transferred to Worklytics.
+These pseudonyms leverage SHA-256 hashing / AES encryption, with salt/keys that are known only to your organization and never transferred to Worklytics.
 
-Psoxy enforces that Worklytics can only access API endpoints you've configured ([principle of least
-privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege)) using HTTP methods you allow (eg, limit to `GET` to enforce read-only for RESTful APIs).
+Psoxy enforces that Worklytics can only access API endpoints you've configured ([principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege)) using HTTP methods you allow (eg, limit to `GET` to enforce read-only for RESTful APIs).
 
-For data sources APIs which require keys/secrets for authentication, such values remain stored in
-your premises and are never accessible to Worklytics.
+For data sources APIs which require keys/secrets for authentication, such values remain stored in your premises and are never accessible to Worklytics.
 
-You authorize your Worklytics tenant to access your proxy instance(s) via the IAM platform of your
-cloud host.
+You authorize your Worklytics tenant to access your proxy instance(s) via the IAM platform of your cloud host.
 
 Worklytics authenticates your tenant with your cloud host via [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation). This eliminates the need for any secrets to be exchanged between your organization and Worklytics, or the use any API keys/certificates for Worklytics which you would need to rotate.
 
 See also: [API Data Sanitization](configuration/api-data-sanitization.md)
 
 ## Supported Data Sources
-As of March 2023, the following sources can be connected to Worklytics via psoxy.
+As of July 2025, the following sources can be connected to Worklytics via psoxy.
 
-Note: Some sources require specific licenses to transfer data via the APIs/endpoints used by Worklytics, or impose some per API request costs for such transfers.
+Note: Some sources require specific licenses to transfer data via the APIs/endpoints used by Worklytics, or impose some per API request costs/rate limits for such transfers. Inclusion of the source in the list below does not represent or warrant retrieval of your data using Psoxy from the source via our provided connectors.
 
 ### Google Workspace (formerly GSuite)
 
@@ -114,7 +110,7 @@ NOTE: usage of the Microsoft Teams APIs may be billable, depending on your Micro
 
 See details: [sources/microsoft-365/README.md](sources/microsoft-365/README.md)
 
-### Github
+### GitHub
 
 Check the documentation to use the right permissions and the right authentication flow per connector.
 
@@ -214,11 +210,10 @@ You will need all the following in your deployment environment (eg, your laptop)
 | Tool                                         | Version              | Test Command          |
 |----------------------------------------------|----------------------|-----------------------|
 | [git](https://git-scm.com/)                  | 2.17+                | `git --version`       |
-| [Maven](https://maven.apache.org/)           | 3.6+                 | `mvn -v`              |
-| [Java JDK 17+](https://openjdk.org/install/) | 17, 21 (see notes) | `mvn -v \| grep Java` |
+| [Maven](https://maven.apache.org/)           | 3.6+ ; 3.9.10+ required for java 24  | `mvn -v`              |
+| [Java JDK 17+](https://openjdk.org/install/) | 17, 21, 24 (see notes) | `mvn -v \| grep Java` |
 | [Terraform](https://www.terraform.io/)       | 1.6+, < 2.0          | `terraform version`   |
 
-NOTE: as of Apr 8, 2024, although Java 24 has been released Maven 3.9.9 is not compatible with it. Maven has fixed this, but has yet to release a version 3.9.10 or 4.0.x with the fix. Until then, we don't officially support Java 24.
 
 NOTE: we will support Java versions for duration of official support windows, in particular the LTS versions. Minor versions, such as 18-20, 22-23 which are out of official support, may work but are not routinely tested.