Class CryptoReplaceFfxFpeConfig.Builder (3.44.0)

public static final class CryptoReplaceFfxFpeConfig.Builder extends GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder> implements CryptoReplaceFfxFpeConfigOrBuilder

Replaces an identifier with a surrogate using Format Preserving Encryption (FPE) with the FFX mode of operation; however when used in the ReidentifyContent API method, it serves the opposite function by reversing the surrogate back into the original identifier. The identifier must be encoded as ASCII. For a given crypto key and context, the same identifier will be replaced with the same surrogate. Identifiers must be at least two characters long. In the case that the identifier is the empty string, it will be skipped. See https://cloud.google.com/sensitive-data-protection/docs/pseudonymization to learn more.

Note: We recommend using CryptoDeterministicConfig for all use cases which do not require preserving the input alphabet space and size, plus warrant referential integrity.

Protobuf type google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig

Static Methods

getDescriptor()

public static final Descriptors.Descriptor getDescriptor()
Returns
TypeDescription
Descriptor

Methods

addRepeatedField(Descriptors.FieldDescriptor field, Object value)

public CryptoReplaceFfxFpeConfig.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

build()

public CryptoReplaceFfxFpeConfig build()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig

buildPartial()

public CryptoReplaceFfxFpeConfig buildPartial()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig

clear()

public CryptoReplaceFfxFpeConfig.Builder clear()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

clearAlphabet()

public CryptoReplaceFfxFpeConfig.Builder clearAlphabet()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

clearCommonAlphabet()

public CryptoReplaceFfxFpeConfig.Builder clearCommonAlphabet()

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

clearContext()

public CryptoReplaceFfxFpeConfig.Builder clearContext()

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

clearCryptoKey()

public CryptoReplaceFfxFpeConfig.Builder clearCryptoKey()

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

clearCustomAlphabet()

public CryptoReplaceFfxFpeConfig.Builder clearCustomAlphabet()

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

clearField(Descriptors.FieldDescriptor field)

public CryptoReplaceFfxFpeConfig.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
NameDescription
fieldFieldDescriptor
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

clearOneof(Descriptors.OneofDescriptor oneof)

public CryptoReplaceFfxFpeConfig.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
NameDescription
oneofOneofDescriptor
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

clearRadix()

public CryptoReplaceFfxFpeConfig.Builder clearRadix()

The native way to select the alphabet. Must be in the range [2, 95].

int32 radix = 6;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

clearSurrogateInfoType()

public CryptoReplaceFfxFpeConfig.Builder clearSurrogateInfoType()

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

clone()

public CryptoReplaceFfxFpeConfig.Builder clone()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

getAlphabetCase()

public CryptoReplaceFfxFpeConfig.AlphabetCase getAlphabetCase()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.AlphabetCase

getCommonAlphabet()

public CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet getCommonAlphabet()

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet

The commonAlphabet.

getCommonAlphabetValue()

public int getCommonAlphabetValue()

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Returns
TypeDescription
int

The enum numeric value on the wire for commonAlphabet.

getContext()

public FieldId getContext()

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Returns
TypeDescription
FieldId

The context.

getContextBuilder()

public FieldId.Builder getContextBuilder()

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Returns
TypeDescription
FieldId.Builder

getContextOrBuilder()

public FieldIdOrBuilder getContextOrBuilder()

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Returns
TypeDescription
FieldIdOrBuilder

getCryptoKey()

public CryptoKey getCryptoKey()

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
CryptoKey

The cryptoKey.

getCryptoKeyBuilder()

public CryptoKey.Builder getCryptoKeyBuilder()

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
CryptoKey.Builder

getCryptoKeyOrBuilder()

public CryptoKeyOrBuilder getCryptoKeyOrBuilder()

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
CryptoKeyOrBuilder

getCustomAlphabet()

public String getCustomAlphabet()

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Returns
TypeDescription
String

The customAlphabet.

getCustomAlphabetBytes()

public ByteString getCustomAlphabetBytes()

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Returns
TypeDescription
ByteString

The bytes for customAlphabet.

getDefaultInstanceForType()

public CryptoReplaceFfxFpeConfig getDefaultInstanceForType()
Returns
TypeDescription
CryptoReplaceFfxFpeConfig

getDescriptorForType()

public Descriptors.Descriptor getDescriptorForType()
Returns
TypeDescription
Descriptor
Overrides

getRadix()

public int getRadix()

The native way to select the alphabet. Must be in the range [2, 95].

int32 radix = 6;

Returns
TypeDescription
int

The radix.

getSurrogateInfoType()

public InfoType getSurrogateInfoType()

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Returns
TypeDescription
InfoType

The surrogateInfoType.

getSurrogateInfoTypeBuilder()

public InfoType.Builder getSurrogateInfoTypeBuilder()

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Returns
TypeDescription
InfoType.Builder

getSurrogateInfoTypeOrBuilder()

public InfoTypeOrBuilder getSurrogateInfoTypeOrBuilder()

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Returns
TypeDescription
InfoTypeOrBuilder

hasCommonAlphabet()

public boolean hasCommonAlphabet()

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Returns
TypeDescription
boolean

Whether the commonAlphabet field is set.

hasContext()

public boolean hasContext()

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Returns
TypeDescription
boolean

Whether the context field is set.

hasCryptoKey()

public boolean hasCryptoKey()

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
boolean

Whether the cryptoKey field is set.

hasCustomAlphabet()

public boolean hasCustomAlphabet()

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Returns
TypeDescription
boolean

Whether the customAlphabet field is set.

hasRadix()

public boolean hasRadix()

The native way to select the alphabet. Must be in the range [2, 95].

int32 radix = 6;

Returns
TypeDescription
boolean

Whether the radix field is set.

hasSurrogateInfoType()

public boolean hasSurrogateInfoType()

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Returns
TypeDescription
boolean

Whether the surrogateInfoType field is set.

internalGetFieldAccessorTable()

protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
TypeDescription
FieldAccessorTable
Overrides

isInitialized()

public final boolean isInitialized()
Returns
TypeDescription
boolean
Overrides

mergeContext(FieldId value)

public CryptoReplaceFfxFpeConfig.Builder mergeContext(FieldId value)

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Parameter
NameDescription
valueFieldId
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

mergeCryptoKey(CryptoKey value)

public CryptoReplaceFfxFpeConfig.Builder mergeCryptoKey(CryptoKey value)

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
valueCryptoKey
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

mergeFrom(CryptoReplaceFfxFpeConfig other)

public CryptoReplaceFfxFpeConfig.Builder mergeFrom(CryptoReplaceFfxFpeConfig other)
Parameter
NameDescription
otherCryptoReplaceFfxFpeConfig
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

public CryptoReplaceFfxFpeConfig.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
NameDescription
inputCodedInputStream
extensionRegistryExtensionRegistryLite
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides
Exceptions
TypeDescription
IOException

mergeFrom(Message other)

public CryptoReplaceFfxFpeConfig.Builder mergeFrom(Message other)
Parameter
NameDescription
otherMessage
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

mergeSurrogateInfoType(InfoType value)

public CryptoReplaceFfxFpeConfig.Builder mergeSurrogateInfoType(InfoType value)

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Parameter
NameDescription
valueInfoType
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

mergeUnknownFields(UnknownFieldSet unknownFields)

public final CryptoReplaceFfxFpeConfig.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)

public CryptoReplaceFfxFpeConfig.Builder setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Parameter
NameDescription
valueCryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet

The commonAlphabet to set.

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

setCommonAlphabetValue(int value)

public CryptoReplaceFfxFpeConfig.Builder setCommonAlphabetValue(int value)

Common alphabets.

.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;

Parameter
NameDescription
valueint

The enum numeric value on the wire for commonAlphabet to set.

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

setContext(FieldId value)

public CryptoReplaceFfxFpeConfig.Builder setContext(FieldId value)

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Parameter
NameDescription
valueFieldId
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setContext(FieldId.Builder builderForValue)

public CryptoReplaceFfxFpeConfig.Builder setContext(FieldId.Builder builderForValue)

The 'tweak', a context may be used for higher security since the same identifier in two different contexts won't be given the same surrogate. If the context is not set, a default tweak will be used.

If the context is set but:

  1. there is no record present when transforming a given value or
  2. the field is not present when transforming a given value,

    a default tweak will be used.

    Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems. Currently, the referenced field may be of value type integer or string.

    The tweak is constructed as a sequence of bytes in big endian byte order such that:

  3. a 64 bit integer is encoded followed by a single byte of value 1

  4. a string is encoded in UTF-8 format followed by a single byte of value 2

.google.privacy.dlp.v2.FieldId context = 2;

Parameter
NameDescription
builderForValueFieldId.Builder
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setCryptoKey(CryptoKey value)

public CryptoReplaceFfxFpeConfig.Builder setCryptoKey(CryptoKey value)

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
valueCryptoKey
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setCryptoKey(CryptoKey.Builder builderForValue)

public CryptoReplaceFfxFpeConfig.Builder setCryptoKey(CryptoKey.Builder builderForValue)

Required. The key used by the encryption algorithm.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
builderForValueCryptoKey.Builder
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setCustomAlphabet(String value)

public CryptoReplaceFfxFpeConfig.Builder setCustomAlphabet(String value)

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Parameter
NameDescription
valueString

The customAlphabet to set.

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

setCustomAlphabetBytes(ByteString value)

public CryptoReplaceFfxFpeConfig.Builder setCustomAlphabetBytes(ByteString value)

This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: <code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&*()_-+={[}]|\:;"'<,>.?/</code>

string custom_alphabet = 5;

Parameter
NameDescription
valueByteString

The bytes for customAlphabet to set.

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

setField(Descriptors.FieldDescriptor field, Object value)

public CryptoReplaceFfxFpeConfig.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

setRadix(int value)

public CryptoReplaceFfxFpeConfig.Builder setRadix(int value)

The native way to select the alphabet. Must be in the range [2, 95].

int32 radix = 6;

Parameter
NameDescription
valueint

The radix to set.

Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

This builder for chaining.

setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

public CryptoReplaceFfxFpeConfig.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
NameDescription
fieldFieldDescriptor
indexint
valueObject
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides

setSurrogateInfoType(InfoType value)

public CryptoReplaceFfxFpeConfig.Builder setSurrogateInfoType(InfoType value)

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Parameter
NameDescription
valueInfoType
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setSurrogateInfoType(InfoType.Builder builderForValue)

public CryptoReplaceFfxFpeConfig.Builder setSurrogateInfoType(InfoType.Builder builderForValue)

The custom infoType to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom infoType followed by the number of characters comprising the surrogate. The following scheme defines the format: info_type_name(surrogate_character_count):surrogate

For example, if the name of custom infoType is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom infoType SurrogateType. This facilitates reversal of the surrogate when it occurs in free text.

In order for inspection to work properly, the name of this infoType must not occur naturally anywhere in your data; otherwise, inspection may find a surrogate that does not correspond to an actual identifier. Therefore, choose your custom infoType name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE

.google.privacy.dlp.v2.InfoType surrogate_info_type = 8;

Parameter
NameDescription
builderForValueInfoType.Builder
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder

setUnknownFields(UnknownFieldSet unknownFields)

public final CryptoReplaceFfxFpeConfig.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
CryptoReplaceFfxFpeConfig.Builder
Overrides