public static final class CryptoReplaceFfxFpeConfig.Builder extends GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder> implements CryptoReplaceFfxFpeConfigOrBuilder
Replaces an identifier with a surrogate using 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 [Pseudonymization](/dlp/docs/pseudonymization) for example usage.Protobuf type
google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig| Modifier and Type | Method and Description |
|---|---|
CryptoReplaceFfxFpeConfig.Builder |
addRepeatedField(Descriptors.FieldDescriptor field,
java.lang.Object value) |
CryptoReplaceFfxFpeConfig |
build() |
CryptoReplaceFfxFpeConfig |
buildPartial() |
CryptoReplaceFfxFpeConfig.Builder |
clear() |
CryptoReplaceFfxFpeConfig.Builder |
clearAlphabet() |
CryptoReplaceFfxFpeConfig.Builder |
clearCommonAlphabet()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4; |
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()
The key used by the encryption algorithm.
|
CryptoReplaceFfxFpeConfig.Builder |
clearCustomAlphabet()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
clearField(Descriptors.FieldDescriptor field) |
CryptoReplaceFfxFpeConfig.Builder |
clearOneof(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()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4; |
int |
getCommonAlphabetValue()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4; |
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()
The key used by the encryption algorithm.
|
CryptoKey.Builder |
getCryptoKeyBuilder()
The key used by the encryption algorithm.
|
CryptoKeyOrBuilder |
getCryptoKeyOrBuilder()
The key used by the encryption algorithm.
|
java.lang.String |
getCustomAlphabet()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
ByteString |
getCustomAlphabetBytes()
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig |
getDefaultInstanceForType() |
static Descriptors.Descriptor |
getDescriptor() |
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 |
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()
The key used by the encryption algorithm.
|
boolean |
hasSurrogateInfoType()
The custom infoType to annotate the surrogate with.
|
protected 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)
The key used by the encryption algorithm.
|
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(CodedInputStream input,
ExtensionRegistryLite extensionRegistry) |
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(CryptoReplaceFfxFpeConfig other) |
CryptoReplaceFfxFpeConfig.Builder |
mergeFrom(Message other) |
CryptoReplaceFfxFpeConfig.Builder |
mergeSurrogateInfoType(InfoType value)
The custom infoType to annotate the surrogate with.
|
CryptoReplaceFfxFpeConfig.Builder |
mergeUnknownFields(UnknownFieldSet unknownFields) |
CryptoReplaceFfxFpeConfig.Builder |
setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4; |
CryptoReplaceFfxFpeConfig.Builder |
setCommonAlphabetValue(int value)
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4; |
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)
The key used by the encryption algorithm.
|
CryptoReplaceFfxFpeConfig.Builder |
setCryptoKey(CryptoKey value)
The key used by the encryption algorithm.
|
CryptoReplaceFfxFpeConfig.Builder |
setCustomAlphabet(java.lang.String value)
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
setCustomAlphabetBytes(ByteString value)
This is supported by mapping these to the alphanumeric characters
that the FFX mode natively supports.
|
CryptoReplaceFfxFpeConfig.Builder |
setField(Descriptors.FieldDescriptor field,
java.lang.Object value) |
CryptoReplaceFfxFpeConfig.Builder |
setRadix(int value)
The native way to select the alphabet.
|
CryptoReplaceFfxFpeConfig.Builder |
setRepeatedField(Descriptors.FieldDescriptor field,
int index,
java.lang.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(UnknownFieldSet unknownFields) |
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, newBuilderForField, onBuilt, onChanged, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitfindInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofmergeFrompublic static final Descriptors.Descriptor getDescriptor()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clear()
clear in interface Message.Builderclear in interface MessageLite.Builderclear in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface Message.BuildergetDescriptorForType in interface MessageOrBuildergetDescriptorForType in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig getDefaultInstanceForType()
getDefaultInstanceForType in interface MessageLiteOrBuildergetDefaultInstanceForType in interface MessageOrBuilderpublic CryptoReplaceFfxFpeConfig build()
build in interface Message.Builderbuild in interface MessageLite.Builderpublic CryptoReplaceFfxFpeConfig buildPartial()
buildPartial in interface Message.BuilderbuildPartial in interface MessageLite.Builderpublic CryptoReplaceFfxFpeConfig.Builder clone()
clone in interface Message.Builderclone in interface MessageLite.Builderclone in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder setField(Descriptors.FieldDescriptor field, java.lang.Object value)
setField in interface Message.BuildersetField in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clearField(Descriptors.FieldDescriptor field)
clearField in interface Message.BuilderclearField in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder clearOneof(Descriptors.OneofDescriptor oneof)
clearOneof in interface Message.BuilderclearOneof in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, java.lang.Object value)
setRepeatedField in interface Message.BuildersetRepeatedField in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder addRepeatedField(Descriptors.FieldDescriptor field, java.lang.Object value)
addRepeatedField in interface Message.BuilderaddRepeatedField in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(Message other)
mergeFrom in interface Message.BuildermergeFrom in class AbstractMessage.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(CryptoReplaceFfxFpeConfig other)
public final boolean isInitialized()
isInitialized in interface MessageLiteOrBuilderisInitialized in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public CryptoReplaceFfxFpeConfig.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry) throws java.io.IOException
mergeFrom in interface Message.BuildermergeFrom in interface MessageLite.BuildermergeFrom in class AbstractMessage.Builder<CryptoReplaceFfxFpeConfig.Builder>java.io.IOExceptionpublic CryptoReplaceFfxFpeConfig.AlphabetCase getAlphabetCase()
getAlphabetCase in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder clearAlphabet()
public boolean hasCryptoKey()
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;hasCryptoKey in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoKey getCryptoKey()
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;getCryptoKey in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCryptoKey(CryptoKey value)
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;public CryptoReplaceFfxFpeConfig.Builder setCryptoKey(CryptoKey.Builder builderForValue)
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;public CryptoReplaceFfxFpeConfig.Builder mergeCryptoKey(CryptoKey value)
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;public CryptoReplaceFfxFpeConfig.Builder clearCryptoKey()
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;public CryptoKey.Builder getCryptoKeyBuilder()
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;public CryptoKeyOrBuilder getCryptoKeyOrBuilder()
The key used by the encryption algorithm. [required]
.google.privacy.dlp.v2.CryptoKey crypto_key = 1;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 non-structured `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 non-structured `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 non-structured `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 non-structured `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 non-structured `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 non-structured `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 non-structured `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 non-structured `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 int getCommonAlphabetValue()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;getCommonAlphabetValue in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCommonAlphabetValue(int value)
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;public CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet getCommonAlphabet()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;getCommonAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCommonAlphabet(CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet value)
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;public CryptoReplaceFfxFpeConfig.Builder clearCommonAlphabet()
.google.privacy.dlp.v2.CryptoReplaceFfxFpeConfig.FfxCommonNativeAlphabet common_alphabet = 4;public java.lang.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, 62]. This must be encoded as ASCII. The order of characters does not matter.
string custom_alphabet = 5;getCustomAlphabet in interface CryptoReplaceFfxFpeConfigOrBuilderpublic 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, 62]. This must be encoded as ASCII. The order of characters does not matter.
string custom_alphabet = 5;getCustomAlphabetBytes in interface CryptoReplaceFfxFpeConfigOrBuilderpublic CryptoReplaceFfxFpeConfig.Builder setCustomAlphabet(java.lang.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, 62]. This must be encoded as ASCII. The order of characters does not matter.
string custom_alphabet = 5;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, 62]. This must be encoded as ASCII. The order of characters does not matter.
string custom_alphabet = 5;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, 62]. This must be encoded as ASCII. The order of characters does not matter.
string custom_alphabet = 5;public int getRadix()
The native way to select the alphabet. Must be in the range [2, 62].
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, 62].
int32 radix = 6;public CryptoReplaceFfxFpeConfig.Builder clearRadix()
The native way to select the alphabet. Must be in the range [2, 62].
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`](/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`](/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`](/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`](/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`](/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`](/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`](/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`](/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(UnknownFieldSet unknownFields)
setUnknownFields in interface Message.BuildersetUnknownFields in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>public final CryptoReplaceFfxFpeConfig.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
mergeUnknownFields in interface Message.BuildermergeUnknownFields in class GeneratedMessageV3.Builder<CryptoReplaceFfxFpeConfig.Builder>