From bbbaa687eb9abf61eb3d603562dcc101b78df531 Mon Sep 17 00:00:00 2001 From: jzonthemtn Date: Fri, 8 Nov 2024 17:48:32 -0500 Subject: [PATCH] Updating to Phileas 2.9.0-SNAPSHOT and documentation updates. --- docs/docs/api_and_sdks/api.md | 2 +- .../other_features/consistent_anonymization.md | 2 +- .../filters/common_filters/iban-codes.md | 18 +++++++++--------- .../philter/api/model/ResponseSpanTest.java | 6 +++--- pom.xml | 2 +- 5 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/docs/api_and_sdks/api.md b/docs/docs/api_and_sdks/api.md index 05d7db4..b56b604 100644 --- a/docs/docs/api_and_sdks/api.md +++ b/docs/docs/api_and_sdks/api.md @@ -10,4 +10,4 @@ The Philter [SDKs](sdks.md) provide convenient methods for using Philter's API m ## Securing Philter's API -Philter's API supports one-way and two-way SSL/TLS authentication. See the [settings](../settings.md) for more information. +Philter's API supports one-way and two-way SSL/TLS authentication. See Philter's [Settings](../settings.md) for more information. diff --git a/docs/docs/other_features/consistent_anonymization.md b/docs/docs/other_features/consistent_anonymization.md index 109e0c8..c766c1a 100644 --- a/docs/docs/other_features/consistent_anonymization.md +++ b/docs/docs/other_features/consistent_anonymization.md @@ -12,7 +12,7 @@ Consistent anonymization can be done on the document level or on the context lev Enabling consistent anonymization on the context level requires a cache to store the sensitive information and the corresponding replacement values. If a single instance of Philter is running, its internal cache service (enabled by default) is the best choice and no additional configuration is required. -If multiple instances of Philter are deployed together, Philter requires access to a Redis cache service as shown below. See Philter' [Settings](../settings.md) on how to configure the cache. +If multiple instances of Philter are deployed together, Philter requires access to a Redis cache service as shown below. See Philter's [Settings](../settings.md) on how to configure the cache. **When Philter is deployed in a cluster, a Redis cache is required to enable consistent anonymization.** diff --git a/docs/docs/policies/filters/common_filters/iban-codes.md b/docs/docs/policies/filters/common_filters/iban-codes.md index 44446a4..bdf5aaf 100644 --- a/docs/docs/policies/filters/common_filters/iban-codes.md +++ b/docs/docs/policies/filters/common_filters/iban-codes.md @@ -22,15 +22,15 @@ This filter has no required parameters. The filter may have zero or more filter strategies. When no filter strategy is given the default strategy of `REDACT` is used. When multiple filter strategies are given the filter strategies will be applied in order as they are listed. See [Filter Strategies](../../filter_strategies.md) for details. -| Strategy | Description | -| --------------------- |--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `REDACT` | Replace the sensitive text with a placeholder. | -| `RANDOM_REPLACE` | Replace the sensitive text with a similar, random value. | -| `STATIC_REPLACE` | Replace the sensitive text with a given value. | -| `CRYPTO_REPLACE` | Replace the sensitive text with its encrypted value. | -| `HASH_SHA256_REPLACE` | Replace the sensitive text with its SHA256 hash value. | -| `FPE_ENCRYPT_REPLACE` | Replace the sensitive text with a value generated by [format-preserving encryption](filter-strategies.md#fpe) (FPE) | -| `LAST_4` | Replace the sensitive text with just the last four characters of the text. | +| Strategy | Description | +| --------------------- |-----------------------------------------------------------------------------------------------------------------------| +| `REDACT` | Replace the sensitive text with a placeholder. | +| `RANDOM_REPLACE` | Replace the sensitive text with a similar, random value. | +| `STATIC_REPLACE` | Replace the sensitive text with a given value. | +| `CRYPTO_REPLACE` | Replace the sensitive text with its encrypted value. | +| `HASH_SHA256_REPLACE` | Replace the sensitive text with its SHA256 hash value. | +| `FPE_ENCRYPT_REPLACE` | Replace the sensitive text with a value generated by [format-preserving encryption](../../filter_strategies.md) (FPE) | +| `LAST_4` | Replace the sensitive text with just the last four characters of the text. | ### Conditions diff --git a/philter-api/src/test/java/ai/philterd/test/philter/api/model/ResponseSpanTest.java b/philter-api/src/test/java/ai/philterd/test/philter/api/model/ResponseSpanTest.java index c8fec38..60a49c1 100644 --- a/philter-api/src/test/java/ai/philterd/test/philter/api/model/ResponseSpanTest.java +++ b/philter-api/src/test/java/ai/philterd/test/philter/api/model/ResponseSpanTest.java @@ -28,9 +28,9 @@ public void spansJson() { final String[] window = new String[]{}; - final Span span1 = Span.make(1, 6, FilterType.PERSON, "context", "document", 1.0, "test", "***", "", false, true, window); - final Span span2 = Span.make(8, 12, FilterType.PERSON, "context", "document", 1.0, "test", "***", "", false, true, window); - final Span span3 = Span.make(14, 20, FilterType.PERSON, "context", "document", 1.0, "test", "***", "", false, true, window); + final Span span1 = Span.make(1, 6, FilterType.AGE, "context", "document", 1.0, "test", "***", "", false, true, window); + final Span span2 = Span.make(8, 12, FilterType.AGE, "context", "document", 1.0, "test", "***", "", false, true, window); + final Span span3 = Span.make(14, 20, FilterType.AGE, "context", "document", 1.0, "test", "***", "", false, true, window); final List spans = Arrays.asList(span1, span2, span3); diff --git a/pom.xml b/pom.xml index 4ac655c..5ab5529 100644 --- a/pom.xml +++ b/pom.xml @@ -93,7 +93,7 @@ 4.13.2 1.13.3 1.10.19 - 2.8.0 + 2.9.0-SNAPSHOT 1.4.0 3.3.1 6.1.10