- Elasticsearch Guide: other versions:
- What is Elasticsearch?
- What’s new in 7.10
- Getting started with Elasticsearch
- Set up Elasticsearch
- Installing Elasticsearch
- Configuring Elasticsearch
- Setting JVM options
- Secure settings
- Auditing settings
- Circuit breaker settings
- Cluster-level shard allocation and routing settings
- Cross-cluster replication settings
- Discovery and cluster formation settings
- Field data cache settings
- HTTP
- Index lifecycle management settings
- Index management settings
- Index recovery settings
- Indexing buffer settings
- License settings
- Local gateway settings
- Logging
- Machine learning settings
- Monitoring settings
- Node
- Network settings
- Node query cache settings
- Search settings
- Security settings
- Shard request cache settings
- Snapshot lifecycle management settings
- Transforms settings
- Transport
- Thread pools
- Watcher settings
- Important Elasticsearch configuration
- Important System Configuration
- Bootstrap Checks
- Heap size check
- File descriptor check
- Memory lock check
- Maximum number of threads check
- Max file size check
- Maximum size virtual memory check
- Maximum map count check
- Client JVM check
- Use serial collector check
- System call filter check
- OnError and OnOutOfMemoryError checks
- Early-access check
- G1GC check
- All permission check
- Discovery configuration check
- Bootstrap Checks for X-Pack
- Starting Elasticsearch
- Stopping Elasticsearch
- Discovery and cluster formation
- Add and remove nodes in your cluster
- Full-cluster restart and rolling restart
- Remote clusters
- Set up X-Pack
- Configuring X-Pack Java Clients
- Plugins
- Upgrade Elasticsearch
- Index modules
- Mapping
- Text analysis
- Overview
- Concepts
- Configure text analysis
- Built-in analyzer reference
- Tokenizer reference
- Token filter reference
- Apostrophe
- ASCII folding
- CJK bigram
- CJK width
- Classic
- Common grams
- Conditional
- Decimal digit
- Delimited payload
- Dictionary decompounder
- Edge n-gram
- Elision
- Fingerprint
- Flatten graph
- Hunspell
- Hyphenation decompounder
- Keep types
- Keep words
- Keyword marker
- Keyword repeat
- KStem
- Length
- Limit token count
- Lowercase
- MinHash
- Multiplexer
- N-gram
- Normalization
- Pattern capture
- Pattern replace
- Phonetic
- Porter stem
- Predicate script
- Remove duplicates
- Reverse
- Shingle
- Snowball
- Stemmer
- Stemmer override
- Stop
- Synonym
- Synonym graph
- Trim
- Truncate
- Unique
- Uppercase
- Word delimiter
- Word delimiter graph
- Character filters reference
- Normalizers
- Index templates
- Data streams
- Ingest node
- Search your data
- Query DSL
- Aggregations
- Bucket aggregations
- Adjacency matrix
- Auto-interval date histogram
- Children
- Composite
- Date histogram
- Date range
- Diversified sampler
- Filter
- Filters
- Geo-distance
- Geohash grid
- Geotile grid
- Global
- Histogram
- IP range
- Missing
- Nested
- Parent
- Range
- Rare terms
- Reverse nested
- Sampler
- Significant terms
- Significant text
- Terms
- Variable width histogram
- Subtleties of bucketing range fields
- Metrics aggregations
- Pipeline aggregations
- Bucket aggregations
- EQL
- SQL access
- Overview
- Getting Started with SQL
- Conventions and Terminology
- Security
- SQL REST API
- SQL Translate API
- SQL CLI
- SQL JDBC
- SQL ODBC
- SQL Client Applications
- SQL Language
- Functions and Operators
- Comparison Operators
- Logical Operators
- Math Operators
- Cast Operators
- LIKE and RLIKE Operators
- Aggregate Functions
- Grouping Functions
- Date/Time and Interval Functions and Operators
- Full-Text Search Functions
- Mathematical Functions
- String Functions
- Type Conversion Functions
- Geo Functions
- Conditional Functions And Expressions
- System Functions
- Reserved keywords
- SQL Limitations
- Scripting
- Data management
- ILM: Manage the index lifecycle
- Overview
- Concepts
- Automate rollover
- Manage Filebeat time-based indices
- Index lifecycle actions
- Configure a lifecycle policy
- Migrate index allocation filters to node roles
- Resolve lifecycle policy execution errors
- Start and stop index lifecycle management
- Manage existing indices
- Skip rollover
- Restore a managed data stream or index
- Monitor a cluster
- Frozen indices
- Roll up or transform your data
- Set up a cluster for high availability
- Snapshot and restore
- Secure a cluster
- Overview
- Configuring security
- User authentication
- Built-in users
- Internal users
- Token-based authentication services
- Realms
- Realm chains
- Active Directory user authentication
- File-based user authentication
- LDAP user authentication
- Native user authentication
- OpenID Connect authentication
- PKI user authentication
- SAML authentication
- Kerberos authentication
- Integrating with other authentication systems
- Enabling anonymous access
- Controlling the user cache
- Configuring SAML single-sign-on on the Elastic Stack
- Configuring single sign-on to the Elastic Stack using OpenID Connect
- User authorization
- Built-in roles
- Defining roles
- Granting access to Stack Management features
- Security privileges
- Document level security
- Field level security
- Granting privileges for data streams and index aliases
- Mapping users and groups to roles
- Setting up field and document level security
- Submitting requests on behalf of other users
- Configuring authorization delegation
- Customizing roles and authorization
- Enabling audit logging
- Encrypting communications
- Restricting connections with IP filtering
- Cross cluster search, clients, and integrations
- Tutorial: Getting started with security
- Tutorial: Encrypting communications
- Troubleshooting
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Common Kerberos exceptions
- Common SAML issues
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- Failures due to relocation of the configuration files
- Limitations
- Watch for cluster and index events
- Command line tools
- How To
- Glossary of terms
- REST APIs
- API conventions
- Compact and aligned text (CAT) APIs
- cat aliases
- cat allocation
- cat anomaly detectors
- cat count
- cat data frame analytics
- cat datafeeds
- cat fielddata
- cat health
- cat indices
- cat master
- cat nodeattrs
- cat nodes
- cat pending tasks
- cat plugins
- cat recovery
- cat repositories
- cat segments
- cat shards
- cat snapshots
- cat task management
- cat templates
- cat thread pool
- cat trained model
- cat transforms
- Cluster APIs
- Cluster allocation explain
- Cluster get settings
- Cluster health
- Cluster reroute
- Cluster state
- Cluster stats
- Cluster update settings
- Nodes feature usage
- Nodes hot threads
- Nodes info
- Nodes reload secure settings
- Nodes stats
- Pending cluster tasks
- Remote cluster info
- Task management
- Voting configuration exclusions
- Cross-cluster replication APIs
- Data stream APIs
- Document APIs
- Enrich APIs
- Graph explore API
- Index APIs
- Add index alias
- Analyze
- Clear cache
- Clone index
- Close index
- Create index
- Delete index
- Delete index alias
- Delete component template
- Delete index template
- Delete index template (legacy)
- Flush
- Force merge
- Freeze index
- Get component template
- Get field mapping
- Get index
- Get index alias
- Get index settings
- Get index template
- Get index template (legacy)
- Get mapping
- Index alias exists
- Index exists
- Index recovery
- Index segments
- Index shard stores
- Index stats
- Index template exists (legacy)
- Open index
- Put index template
- Put index template (legacy)
- Put component template
- Put mapping
- Refresh
- Rollover index
- Shrink index
- Simulate index
- Simulate template
- Split index
- Synced flush
- Type exists
- Unfreeze index
- Update index alias
- Update index settings
- Resolve index
- List dangling indices
- Import dangling index
- Delete dangling index
- Index lifecycle management APIs
- Ingest APIs
- Info API
- Licensing APIs
- Machine learning anomaly detection APIs
- Add events to calendar
- Add jobs to calendar
- Close jobs
- Create jobs
- Create calendars
- Create datafeeds
- Create filters
- Delete calendars
- Delete datafeeds
- Delete events from calendar
- Delete filters
- Delete forecasts
- Delete jobs
- Delete jobs from calendar
- Delete model snapshots
- Delete expired data
- Estimate model memory
- Find file structure
- Flush jobs
- Forecast jobs
- Get buckets
- Get calendars
- Get categories
- Get datafeeds
- Get datafeed statistics
- Get influencers
- Get jobs
- Get job statistics
- Get machine learning info
- Get model snapshots
- Get overall buckets
- Get scheduled events
- Get filters
- Get records
- Open jobs
- Post data to jobs
- Preview datafeeds
- Revert model snapshots
- Set upgrade mode
- Start datafeeds
- Stop datafeeds
- Update datafeeds
- Update filters
- Update jobs
- Update model snapshots
- Machine learning data frame analytics APIs
- Create data frame analytics jobs
- Create trained models
- Update data frame analytics jobs
- Delete data frame analytics jobs
- Delete trained models
- Evaluate data frame analytics
- Explain data frame analytics
- Get data frame analytics jobs
- Get data frame analytics jobs stats
- Get trained models
- Get trained models stats
- Start data frame analytics jobs
- Stop data frame analytics jobs
- Migration APIs
- Reload search analyzers API
- Repositories metering APIs
- Rollup APIs
- Search APIs
- Searchable snapshots APIs
- Security APIs
- Authenticate
- Change passwords
- Clear cache
- Clear roles cache
- Clear privileges cache
- Clear API key cache
- Create API keys
- Create or update application privileges
- Create or update role mappings
- Create or update roles
- Create or update users
- Delegate PKI authentication
- Delete application privileges
- Delete role mappings
- Delete roles
- Delete users
- Disable users
- Enable users
- Get API key information
- Get application privileges
- Get builtin privileges
- Get role mappings
- Get roles
- Get token
- Get users
- Grant API keys
- Has privileges
- Invalidate API key
- Invalidate token
- OpenID Connect prepare authentication
- OpenID Connect authenticate
- OpenID Connect logout
- SAML prepare authentication
- SAML authenticate
- SAML logout
- SAML invalidate
- SSL certificate
- Snapshot and restore APIs
- Snapshot lifecycle management APIs
- Transform APIs
- Usage API
- Watcher APIs
- Definitions
- Migration guide
- Release notes
- Elasticsearch version 7.10.2
- Elasticsearch version 7.10.1
- Elasticsearch version 7.10.0
- Elasticsearch version 7.9.3
- Elasticsearch version 7.9.2
- Elasticsearch version 7.9.1
- Elasticsearch version 7.9.0
- Elasticsearch version 7.8.1
- Elasticsearch version 7.8.0
- Elasticsearch version 7.7.1
- Elasticsearch version 7.7.0
- Elasticsearch version 7.6.2
- Elasticsearch version 7.6.1
- Elasticsearch version 7.6.0
- Elasticsearch version 7.5.2
- Elasticsearch version 7.5.1
- Elasticsearch version 7.5.0
- Elasticsearch version 7.4.2
- Elasticsearch version 7.4.1
- Elasticsearch version 7.4.0
- Elasticsearch version 7.3.2
- Elasticsearch version 7.3.1
- Elasticsearch version 7.3.0
- Elasticsearch version 7.2.1
- Elasticsearch version 7.2.0
- Elasticsearch version 7.1.1
- Elasticsearch version 7.1.0
- Elasticsearch version 7.0.0
- Elasticsearch version 7.0.0-rc2
- Elasticsearch version 7.0.0-rc1
- Elasticsearch version 7.0.0-beta1
- Elasticsearch version 7.0.0-alpha2
- Elasticsearch version 7.0.0-alpha1
- Dependencies and versions
Audit event types
editAudit event types
editWhen you are auditing security events, each request can generate multiple audit events.
The following is a list of the events that can be generated:
|
Logged when a request is denied due to a missing authentication token. |
||
|
Logged when a user successfully authenticates. |
||
|
Logged when the authentication token cannot be matched to a known user. |
||
|
Logged for every realm that fails to present a valid
authentication token. |
||
|
Logged when an authenticated user attempts to execute an action they do not have the necessary privilege to perform. |
||
|
Logged when an authenticated user attempts to execute
an action they have the necessary privilege to perform.
When the |
||
|
Logged when an authenticated user attempts to run as another user that they have the necessary privileges to do. |
||
|
Logged when an authenticated user attempts to run as another user action they do not have the necessary privilege to do so. |
||
|
Logged when the security features detect that the request has
been tampered with. Typically relates to |
||
|
Logged when an incoming TCP connection passes the IP Filter for a specific profile. |
||
|
Logged when an incoming TCP connection does not pass the IP Filter for a specific profile. |
Audit event attributes
editIn 6.5.0, there is a new logfile
audit output format.
This format also brings in a few changes for audit event attributes.
The new format is output to the <clustername>_audit.json
file.
The audit entries are formatted as flat JSON documents (that is to say, no
nested objects), one per line. Hence, the attribute names are JSON keys and they
follow a dotted name syntax. Any attributes that lack a value (null
) are not
output.
The following list shows attributes that are common to all audit events.
Their names and values are analogous to those in the deprecated logfile
or
index
output formats. However, it is expected that the formats will evolve
independently during the 6.x releases, so it is advisable to follow the attribute
descriptions for the format that you are using.
-
@timestamp
- The time, in ISO9601 format, when the event occurred.
-
node.name
-
The name of the node. This can be changed
in the
elasticsearch.yml
config file. -
node.id
- The node id. This is automatically generated and is persistent across full cluster restarts.
-
host.ip
- The bound IP address of the node, with which the node can be communicated with.
-
host.name
- The unresolved node’s hostname.
-
origin.address
- The source IP address of the request associated with this event. This could be the address of the remote client, the address of another cluster node, or the local node’s bound address, if the request originated locally. Unless the remote client connects directly to the cluster, the client address will actually be the address of the first OSI layer 3 proxy in front of the cluster.
-
origin.type
-
The origin type of the request associated with this event:
rest
(request originated from a REST API request),transport
(request was received on the transport channel), orlocal_node
(the local node issued the request). -
event.type
-
The internal processing layer that generated the event:
rest
,transport
orip_filter
. This is different fromorigin.type
because a request originating from the REST API is translated to a number of transport messages, generating audit events withorigin.type: rest
andevent.type: transport
. -
event.action
-
The type of event that occurred:
anonymous_access_denied
,authentication_failed
,authentication_success
,realm_authentication_failed
,access_denied
,access_granted
,connection_denied
,connection_granted
,tampered_request
,run_as_denied
, orrun_as_granted
. -
opaque_id
-
The value of the
X-Opaque-Id
HTTP header (if present) of the request associated with this event. This header can be used freely by the client to mark API calls, as it has no semantics in Elasticsearch. -
x_forwarded_for
-
The verbatim value of the
X-Forwarded-For
HTTP request header (if present) of the request associated with the audit event. This header is commonly added by proxies when they forward requests and the value is the address of the proxied client. When a request crosses multiple proxies the header is a comma delimited list with the last value being the address of the second to last proxy server (the address of the last proxy server is designated by theorigin.address
field).
Audit event attributes of the REST event type
editThe events with event.type
equal to rest
have one of the following event.action
attribute values: authentication_success
, anonymous_access_denied
, authentication_failed
,
realm_authentication_failed
, tampered_request
or run_as_denied
.
These event types also have the following extra attributes (in addition to the
common ones):
-
url.path
- The path part of the URL (between the port and the query string) of the REST request associated with this event. This is URL encoded.
-
url.query
- The query part of the URL (after "?", if present) of the REST request associated with this event. This is URL encoded.
-
request.method
- The HTTP method of the REST request associated with this event. It is one of GET, POST, PUT, DELETE, OPTIONS, HEAD, PATCH, TRACE and CONNECT.
-
request.body
- The full content of the REST request associated with this event, if enabled. This contains the query body. The body is escaped according to the JSON RFC 4627.
Audit event attributes of the transport event type
editThe events with event.type
equal to transport
have one of the following event.action
attribute values: authentication_success
, anonymous_access_denied
, authentication_failed
,
realm_authentication_failed
, access_granted
, access_denied
, run_as_granted
,
run_as_denied
, or tampered_request
.
These event types also have the following extra attributes (in addition to the common
ones):
-
action
- The name of the transport action that was executed. This is like the URL for a REST request.
-
indices
- The indices names array that the request associated with this event pertains to (when applicable).
-
request.name
- The name of the request handler that was executed.
Audit event attributes of the ip_filter event type
editThe events with event.type
equal to ip_filter
have one of the following event.action
attribute values: connection_granted
or connection_denied
.
These event types also have the following extra attributes (in addition to the common
ones):
-
transport_profile
- The transport profile the request targeted.
-
rule
- The IP filtering rule that denied the request.
Extra audit event attributes for specific events
editThere are a few events that have some more attributes in addition to those that have been previously described:
-
authentication_success
:-
realm
-
The name of the realm that successfully authenticated the user.
If authenticated using an API key, this is the special value of
_es_api_key
. This is a shorthand attribute for the same information that is described by theuser.realm
,user.run_by.realm
andauthentication.type
attributes. -
user.name
- The name of the effective user. This is usually the same as the authenticated user, but if using the run as authorization functionality this instead denotes the name of the impersonated user. If authenticated using an API key, this is the name of the API key owner.
-
user.realm
- Name of the realm to which the effective user belongs. If authenticated using an API key, this is the name of the realm to which the API key owner belongs.
-
user.run_by.name
- This attribute is present only if the request is using the run as authorization functionality and denotes the name of the authenticated user, which is also known as the impersonator.
-
user.run_by.realm
- Name of the realm to which the authenticated (impersonator) user belongs. This attribute is provided only if the request uses the run as authorization functionality.
-
authentication.type
-
Method used to authenticate the user.
Possible values are
REALM
,API_KEY
,TOKEN
,ANONYMOUS
orINTERNAL
. -
api_key.id
- API key ID returned by the create API key request. This attribute is only provided for authentication using an API key.
-
api_key.name
- API key name provided in the create API key request. This attribute is only provided for authentication using an API key.
-
-
authentication_failed
:-
user.name
- The name of the user that failed authentication. If the request authentication token is invalid or unparsable, this information might be missing.
-
-
realm_authentication_failed
:-
user.name
- The name of the user that failed authentication.
-
realm
- The name of the realm that rejected this authentication. This event is generated for each consulted realm in the chain.
-
-
run_as_denied
andrun_as_granted
:-
user.roles
- The role names of the user as an array.
-
user.name
- The name of the authenticated user which is being granted or denied the impersonation action.
-
user.realm
- The realm name that the authenticated user belongs to.
-
user.run_as.name
- The name of the user as which the impersonation action is granted or denied.
-
user.run_as.realm
- The realm name of that the impersonated user belongs to.
-
-
access_granted
andaccess_denied
:-
user.roles
- The role names of the user as an array. If authenticated using an API key, this contains the role names of the API key owner.
-
user.name
- The name of the effective user. This is usually the same as the authenticated user, but if using the run as authorization functionality this instead denotes the name of the impersonated user. If authenticated using an API key, this is the name of the API key owner.
-
user.realm
- Name of the realm to which the effective user belongs. If authenticated using an API key, this is the name of the realm to which the API key owner belongs.
-
user.run_by.name
- This attribute is present only if the request is using the run as authorization functionality and denoted the name of the authenticated user, which is also known as the impersonator.
-
user.run_by.realm
- This attribute is present only if the request is using the run as authorization functionality and denotes the name of the realm that the authenticated (impersonator) user belongs to.
-
authentication.type
-
Method used to authenticate the user.
Possible values are
REALM
,API_KEY
,TOKEN
,ANONYMOUS
orINTERNAL
. -
api_key.id
- API key ID returned by the create API key request. This attribute is only provided for authentication using an API key.
-
api_key.name
- API key name provided in the create API key request. This attribute is only provided for authentication using an API key.
-
Audit event attributes for the deprecated formats
editThe following table shows the common attributes that can be associated with
every event, when it is output to the <clustername>_access.log
file.
Table 73. Common attributes
Attribute | Description |
---|---|
|
When the event occurred. |
|
The name of the node. |
|
The hostname of the node. |
|
The IP address of the node. |
|
The layer from which this event originated: |
|
The type of event that occurred: |
These are positional attributes, which are printed at the beginning of each log line and are not adjoined by the attribute name.
The attribute origin_address
is also common to every audit event. It is always
named, that is, it is not positional. It denotes the source IP address of the
request associated with this event. This might be the address of the client, the
address of another cluster node, or the local node’s bound address (if the request
originated locally). Unless the client connects directly to the cluster, the
client address is the address of the first OSI layer 3 proxy in front of the
cluster.
In addition, every event might have the opaque_id
attribute, with the value as
it has been passed in by the X-Opaque-Id
HTTP request header. This header can
be used freely by the client to mark API calls, as it has no semantics in
Elasticsearch. Every audit event, generated as part of handling a request thus
marked, contains the opaque_id
attribute.
The following tables show the attributes that can are associated with each type of event, in addition to the common ones previously described:
Table 74. REST anonymous_access_denied attributes
Attribute | Description |
---|---|
|
The REST endpoint URI. |
|
The body of the request, if enabled. |
Table 75. REST authentication_success attributes
Attribute | Description |
---|---|
|
The effective (impersonated) username. Usually this is the same as the authenticated username. |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective user is the same as the
authenticated one, which is indicated by the |
|
The realm that authenticated the user. |
|
The REST endpoint URI. |
|
The REST URI query parameters. |
|
The body of the request, if enabled. |
Table 76. REST authentication_failed attributes
Attribute | Description |
---|---|
|
The principal (username) that failed authentication. If the request’s authentication token is invalid, this information might be missing. |
|
The REST endpoint URI. |
|
The body of the request, if enabled. |
Table 77. REST realm_authentication_failed attributes
Attribute | Description |
---|---|
|
The realm that failed to authenticate the user. A separate entry is logged for each consulted realm. |
|
The principal (username) that failed authentication. |
|
The REST endpoint URI. |
|
The body of the request, if enabled. |
Table 78. REST tampered_request attributes
Attribute | Description |
---|---|
|
The REST endpoint URI. |
|
The body of the request, if enabled. |
Table 79. Transport anonymous_access_denied attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 80. Transport authentication_success attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The effective (impersonated) username. Usually this is the same as the authenticated username. |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective and the authenticated
users are equivalent and are indicated by the
|
|
The realm that authenticated the user. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 81. Transport authentication_failed attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The effective (impersonated) username. Usually this is the same as the authenticated username. If the request’s authentication token is invalid, this information might be missing. |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective and the authenticated
users are equivalent and are indicated by the
|
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 82. Transport realm_authentication_failed attributes
Attribute | Description |
---|---|
|
The realm that failed to authenticate the user. A separate entry is logged for each consulted realm. |
|
Where the request originated: |
|
The principal (username) that failed authentication. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 83. Transport access_granted attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The effective (impersonated) username for which authorization succeeded. Unless the request is using the run as authorization functionality, the effective and authenticated usernames are equivalent. |
|
The realm name that |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective and the authenticated
usernames are equivalent and are indicated by the
|
|
The realm name that |
|
The set of roles granting permissions. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 84. Transport access_denied attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The effective (impersonated) username for which authorization failed. Unless the request is using the run as authorization functionality, the effective and the authenticated usernames are equivalent. |
|
The realm name that |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective and the authenticated
usernames are equivalent and are indicated by the
|
|
The realm name that |
|
The set of roles granting permissions. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request relates to (when applicable). |
|
The type of request that was executed. |
Table 85. Transport run_as_granted attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The authenticated (impersonator) username for which the impersonation operation was granted. |
|
The realm name that the authenticated user belongs to. |
|
The impersonated username. |
|
The realm name that the impersonated username belongs to. |
|
The set of roles granting permissions. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request relates to (when applicable). |
|
The type of request that was executed. |
Table 86. Transport run_as_denied attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The authenticated (impersonator) username for which the impersonation operation was denied. |
|
The realm name that the authenticated user belongs to. |
|
The impersonated username. |
|
The realm name that the impersonated username belongs to. |
|
The set of roles granting permissions. |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request relates to (when applicable). |
|
The type of request that was executed. |
Table 87. Transport tampered_request attributes
Attribute | Description |
---|---|
|
Where the request originated: |
|
The effective (impersonated) username. Unless the request is using the run as authorization functionality, the effective and the authenticated usernames are equivalent. If the requests’s authentication token is invalid, this information might be missing. |
|
The authenticated (impersonator) username.
This attribute is present only if the request is
using the run as authorization functionality.
Otherwise, the effective and the authenticated usernames
are equivalent and are indicated by the |
|
The name of the action that was executed. |
|
A comma-separated list of indices this request pertains to (when applicable). |
|
The type of request that was executed. |
Table 88. IP filter connection_granted attributes
Attribute | Description |
---|---|
|
The transport profile the request targeted. |
|
The IP filtering rule that granted the request. |
Table 89. IP filter connection_denied attributes
Attribute | Description |
---|---|
|
The transport profile the request targeted. |
|
The IP filtering rule that denied the request. |
On this page