public static final class CryptoReplaceFfxFpeConfig.Builder extends com.google.protobuf.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/dlp/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| Modifier and Type | Method and Description |
|---|---|
CryptoReplaceFfxFpeConfig.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
CryptoReplaceFfxFpeConfig |
build() |
CryptoReplaceFfxFpeConfig |
buildPartial() |
CryptoReplaceFfxFpeConfig.Builder |
clear() |
CryptoReplaceFfxFpeConfig.Builder |
clearAlphabet() |
CryptoReplaceFfxFpeConfig.Builder |
clearCommonAlphabet()
Common alphabets.
|
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.
|
CryptoReplaceFfxFpeConfig.Builder |
clearCryptoKey()
Required.
|
CryptoReplaceFfxFpeConfig.Builder |
clearCustomAlphabet()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
clearField(com.google.protobuf.Descriptors.FieldDescriptor field) |
CryptoReplaceFfxFpeConfig.Builder |
clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) |
CryptoReplaceFfxFpeConfig.Builder |
clearRadix()
The native way to select the alphabet.
|
CryptoReplaceFfxFpeConfig.Builder |
clearSurrogateInfoType()
The custom infoType to annotate the surrogate with.
|
CryptoReplaceFfxFpeConfig.Builder |
clone() |
CryptoReplaceFfxFpeConfig.AlphabetCase |
getAlphabetCase() |
CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet |
getCommonAlphabet()
Common alphabets.
|
int |
getCommonAlphabetValue()
Common alphabets.
|
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.
|
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.
|
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.
|
CryptoKey |
getCryptoKey()
Required.
|
CryptoKey.Builder |
getCryptoKeyBuilder()
Required.
|
CryptoKeyOrBuilder |
getCryptoKeyOrBuilder()
Required.
|
String |
getCustomAlphabet()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
com.google.protobuf.ByteString |
getCustomAlphabetBytes()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
int |
getRadix()
The native way to select the alphabet.
|
InfoType |
getSurrogateInfoType()
The custom infoType to annotate the surrogate with.
|
InfoType.Builder |
getSurrogateInfoTypeBuilder()
The custom infoType to annotate the surrogate with.
|
InfoTypeOrBuilder |
getSurrogateInfoTypeOrBuilder()
The custom infoType to annotate the surrogate with.
|
boolean |
hasCommonAlphabet()
Common alphabets.
|
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.
|
boolean |
hasCryptoKey()
Required.
|
boolean |
hasCustomAlphabet()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
boolean |
hasRadix()
The native way to select the alphabet.
|
boolean |
hasSurrogateInfoType()
The custom infoType to annotate the surrogate with.
|
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
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.
|
CryptoReplaceFfxFpeConfig.Builder |
mergeCryptoKey(CryptoKey value)
Required.
|
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(CryptoReplaceFfxFpeConfig other) |
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(com.google.protobuf.Message other) |
CryptoReplaceFfxFpeConfig.Builder |
mergeSurrogateInfoType(InfoType value)
The custom infoType to annotate the surrogate with.
|
CryptoReplaceFfxFpeConfig.Builder |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
CryptoReplaceFfxFpeConfig.Builder |
setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)
Common alphabets.
|
CryptoReplaceFfxFpeConfig.Builder |
setCommonAlphabetValue(int value)
Common alphabets.
|
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.
|
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.
|
CryptoReplaceFfxFpeConfig.Builder |
setCryptoKey(CryptoKey.Builder builderForValue)
Required.
|
CryptoReplaceFfxFpeConfig.Builder |
setCryptoKey(CryptoKey value)
Required.
|
CryptoReplaceFfxFpeConfig.Builder |
setCustomAlphabet(String value)
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
setCustomAlphabetBytes(com.google.protobuf.ByteString value)
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
setField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
CryptoReplaceFfxFpeConfig.Builder |
setRadix(int value)
The native way to select the alphabet.
|
CryptoReplaceFfxFpeConfig.Builder |
setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
int index,
Object value) |
CryptoReplaceFfxFpeConfig.Builder |
setSurrogateInfoType(InfoType.Builder builderForValue)
The custom infoType to annotate the surrogate with.
|
CryptoReplaceFfxFpeConfig.Builder |
setSurrogateInfoType(InfoType value)
The custom infoType to annotate the surrogate with.
|
CryptoReplaceFfxFpeConfig.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitfindInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic CryptoReplaceFfxFpeConfig build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic CryptoReplaceFfxFpeConfig buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic CryptoReplaceFfxFpeConfig.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(CryptoReplaceFfxFpeConfig other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<CryptoReplaceFfxFpeConfig.Builder>IOExceptionpublic CryptoReplaceFfxFpeConfig.AlphabetCase getAlphabetCase()
getAlphabetCase in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder clearAlphabet()
public boolean hasCryptoKey()
Required. The key used by the encryption algorithm.
.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];
hasCryptoKey in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoKey getCryptoKey()
Required. The key used by the encryption algorithm.
.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];
getCryptoKey in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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];
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];
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];
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];
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];
public CryptoKeyOrBuilder getCryptoKeyOrBuilder()
Required. The key used by the encryption algorithm.
.google.privacy.dlp.v2.CryptoKey crypto_key = 1 [(.google.api.field_behavior) = REQUIRED];
getCryptoKeyOrBuilder in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;hasContext in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;getContext in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;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 1. 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 `ContentItem`s. 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: - a 64 bit integer is encoded followed by a single byte of value 1 - a string is encoded in UTF-8 format followed by a single byte of value 2
.google.privacy.dlp.v2.FieldId context = 2;getContextOrBuilder in interface CryptoReplaceFfxFpeConfigOrBuilderpublic boolean hasCommonAlphabet()
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
hasCommonAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic int getCommonAlphabetValue()
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
getCommonAlphabetValue in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCommonAlphabetValue(int value)
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
value - The enum numeric value on the wire for commonAlphabet to set.public CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet getCommonAlphabet()
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
getCommonAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
value - The commonAlphabet to set.public CryptoReplaceFfxFpeConfig.Builder clearCommonAlphabet()
Common alphabets.
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;
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;hasCustomAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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;getCustomAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic com.google.protobuf.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;getCustomAlphabetBytes in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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;value - The customAlphabet to set.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;public CryptoReplaceFfxFpeConfig.Builder setCustomAlphabetBytes(com.google.protobuf.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;value - The bytes for customAlphabet to set.public boolean hasRadix()
The native way to select the alphabet. Must be in the range [2, 95].
int32 radix = 6;hasRadix in interface CryptoReplaceFfxFpeConfigOrBuilderpublic int getRadix()
The native way to select the alphabet. Must be in the range [2, 95].
int32 radix = 6;getRadix in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setRadix(int value)
The native way to select the alphabet. Must be in the range [2, 95].
int32 radix = 6;value - The radix to set.public CryptoReplaceFfxFpeConfig.Builder clearRadix()
The native way to select the alphabet. Must be in the range [2, 95].
int32 radix = 6;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;hasSurrogateInfoType in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;getSurrogateInfoType in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;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`](https://cloud.google.com/dlp/docs/reference/rest/v2/InspectConfig#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;getSurrogateInfoTypeOrBuilder in interface CryptoReplaceFfxFpeConfigOrBuilderpublic final CryptoReplaceFfxFpeConfig.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public final CryptoReplaceFfxFpeConfig.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>Copyright © 2022 Google LLC. All rights reserved.