- Home
- Documentation
- Uncategorized
- Data Sources
- xcsh_user_identification (Data Source)
xcsh_user_identification (Data Source)
Retrieves information about user_identification creates a new object in the storage backend for metadata.namespace in F5 Distributed Cloud. This is a read-only data source.
~> Note: For more information, see the F5 Distributed Cloud API documentation.
Example Usage
Section titled “Example Usage”# UserIdentification Data Source Example
terraform { required_version = ">= 1.0"
required_providers { xcsh = { source = "f5-sales-demo/xcsh" version = ">= 0.1.0" } }}
# Look up an existing UserIdentification by namedata "xcsh_user_identification" "example" { name = "example-user-identification" namespace = "staging"}
output "user_identification_id" { value = data.xcsh_user_identification.example.id}Argument Reference
Section titled “Argument Reference”-> Syntax Rule: This provider uses OneOf groups for mutually exclusive options. Fields documented as “Optional Block” use block syntax field_name { ... }. Empty OneOf object attributes use field_name = {}; conditional selection uses condition ? {} : null. Boolean attributes (such as add_hsts and http_redirect) use = true or = false.
🔶 High Risk Operations — Some operations on this resource have high danger level. Destructive operations may require confirmation.
Minimum Configuration
Section titled “Minimum Configuration”Required fields:
namenamespacerules
Example (API format):
apiVersion: v1kind: user_identificationmetadata: name: example-user-id namespace: demo-appspec: rules: - client_ip: {}Metadata Argument Reference
Section titled “Metadata Argument Reference”• name - Required String
Name of the UserIdentification
• namespace - Required String
Namespace where the UserIdentification exists
Attributes Reference
Section titled “Attributes Reference”In addition to all arguments above, the following attributes are exported:
• annotations - Optional Map
Annotations applied to this resource
• description - Optional String
Description of the UserIdentification
• id - Optional String
Unique identifier for the resource
• labels - Optional Map
Labels applied to this resource
• rules - Optional List
Ordered list of rules that are evaluated sequentially against the input fields extracted from an API request in order to determine a user identifier. Evaluation of the rules is terminated once a user identifier has been extracted
A rules block supports the following:
• client_asn - Optional Object
Enable this option
• client_city - Optional Object
Enable this option
• client_country - Optional Object
Enable this option
• client_ip - Optional Object
Enable this option
• client_region - Optional Object
Enable this option
• cookie_name - Optional String
Use the HTTP cookie value for the given name as user
• http_header_name - Optional String
Use the HTTP header value for the given name as user
• ip_and_http_header_name - Optional String
Name of HTTP header from which the value should be extracted
• ip_and_ja4_tls_fingerprint - Optional Object
Enable this option
• ip_and_tls_fingerprint - Optional Object
Enable this option
• ja4_tls_fingerprint - Optional Object
Configuration parameter for ja4 TLS fingerprint
• jwt_claim_name - Optional String
Use the JWT claim value as user identifier
• none - Optional Object
Enable this option
• query_param_key - Optional String
Use the query parameter value for the given key as user
• tls_fingerprint - Optional Object
Configuration parameter for TLS fingerprint
Rules Client Asn
Section titled “Rules Client Asn”A client_asn block (within rules) supports the following:
Rules Client City
Section titled “Rules Client City”A client_city block (within rules) supports the following:
Rules Client Country
Section titled “Rules Client Country”A client_country block (within rules) supports the following:
Rules Client IP
Section titled “Rules Client IP”A client_ip block (within rules) supports the following:
Rules Client Region
Section titled “Rules Client Region”A client_region block (within rules) supports the following:
Rules IP And Ja4 TLS Fingerprint
Section titled “Rules IP And Ja4 TLS Fingerprint”An ip_and_ja4_tls_fingerprint block (within rules) supports the following:
Rules IP And TLS Fingerprint
Section titled “Rules IP And TLS Fingerprint”An ip_and_tls_fingerprint block (within rules) supports the following:
Rules Ja4 TLS Fingerprint
Section titled “Rules Ja4 TLS Fingerprint”A ja4_tls_fingerprint block (within rules) supports the following:
Common Types
Section titled “Common Types”The following type definitions are used throughout this resource. See the full definition here rather than repeated inline.
Object Reference {#common-object-reference}
Section titled “Object Reference {#common-object-reference}”Object references establish a direct reference from one configuration object to another in F5 Distributed Cloud. References use the format tenant/namespace/name.
| Field | Type | Description |
|---|---|---|
name | String | Name of the referenced object |
namespace | String | Namespace containing the referenced object |
tenant | String | Tenant of the referenced object (system-managed) |
Transformers {#common-transformers}
Section titled “Transformers {#common-transformers}”Transformers apply transformations to input values before matching. Multiple transformers can be applied in order.
| Value | Description |
|---|---|
LOWER_CASE | Convert to lowercase |
UPPER_CASE | Convert to uppercase |
BASE64_DECODE | Decodebase64 content |
NORMALIZE_PATH | Normalize URL path |
REMOVE_WHITESPACE | Remove whitespace characters |
URL_DECODE | Decode URL-encoded characters |
TRIM_LEFT | Trim leading whitespace |
TRIM_RIGHT | Trim trailing whitespace |
TRIM | Trim both leading and trailing whitespace |
HTTP Methods {#common-http-methods}
Section titled “HTTP Methods {#common-http-methods}”HTTP methods used for request matching.
| Value | Description |
|---|---|
ANY | Match any HTTP method |
GET | HTTP GET request |
HEAD | HTTP HEAD request |
POST | HTTP POST request |
PUT | HTTP PUT request |
DELETE | HTTP DELETE request |
CONNECT | HTTP CONNECT request |
OPTIONS | HTTP OPTIONS request |
TRACE | HTTP TRACE request |
PATCH | HTTP PATCH request |
COPY | HTTP COPY request (WebDAV) |
TLS Fingerprints {#common-tls-fingerprints}
Section titled “TLS Fingerprints {#common-tls-fingerprints}”TLS fingerprint categories for malicious client detection.
| Value | Description |
|---|---|
TLS_FINGERPRINT_NONE | No fingerprint matching |
ANY_MALICIOUS_FINGERPRINT | Match any known malicious fingerprint |
ADWARE | Adware-associated fingerprints |
DRIDEX | Dridex malware fingerprints |
GOOTKIT | Gootkit malware fingerprints |
RANSOMWARE | Ransomware-associated fingerprints |
TRICKBOT | Trickbot malware fingerprints |
IP Threat Categories {#common-ip-threat-categories}
Section titled “IP Threat Categories {#common-ip-threat-categories}”IP address threat categories for security filtering.
| Value | Description |
|---|---|
SPAM_SOURCES | Known spam sources |
WINDOWS_EXPLOITS | Windows exploit sources |
WEB_ATTACKS | Web attack sources |
BOTNETS | Known botnet IPs |
SCANNERS | Network scanner IPs |
REPUTATION | Poor reputation IPs |
PHISHING | Phishing-related IPs |
PROXY | Anonymous proxy IPs |
MOBILE_THREATS | Mobile threat sources |
TOR_PROXY | Tor exit nodes |
DENIAL_OF_SERVICE | DoS attack sources |
NETWORK | Known bad network ranges |