Use this file to discover all available pages before exploring further.
As you and your team interact with Conduktor, audit events are captured that give a detailed log of actions, providing a centralized visibility of user-related and resource-related events.
The Console audit log events can be browsed, filtered and searched directly via the UI or exported from a Kafka topic for further use (such as maintaining your own audit trail in other systems).Click on an event in the audit log to expose event-specific metadata. Here’s an example of an audit event for a new connector which can include metadata such as custom tags, the cluster, connector name and its ID.Once configured with the correct environment variables, audit log events are also exported to a Kafka topic, allowing you to leverage the benefits of Conduktor when finding a message.
You can export audit log events from a Kafka topic using the Console UI. The exportable events have more detail than the legacy events, providing additional information about the event that has taken place.Learn how to configure audit events for export via configuration properties.The events conform to the CloudEvents specification , a vendor-neutral format that follows the following structure:
The Gateway audit log events are stored in an internal topic. The topic name is configured using GATEWAY_AUDIT_LOG_TOPIC and the feature can be enabled/disabled using GATEWAY_FEATURE_FLAGS_AUDIT. The audit events can be browsed, filtered and searched via Console UI or used to create custom alerts and notifications.Here’s an example of a Gateway audit log event in JSON format, showing a successful authentication attempt to Gateway:
The connection event tracks client connections to Gateway. It captures client information like remote address, which helps with monitoring connections.
The authentication event records the authentication attempts made by clients to Gateway. It records both successful and failed attempts, providing insights into who accessed Gateway.The eventData field contains different messages, depending on the Gateway security mode, Gateway security protocol and the authentication outcome. Here are some common examples:
Security mode
SASL mechanism
Outcome
Event data
Gateway managed
PLAIN
Success
"SUCCESS"
Gateway managed
PLAIN
Failure
"Authentication failed: credentials for user could not be verified. Cause: Invalid username or password"
Gateway managed
PLAIN
Failure
"Authentication failed: credentials for user could not be verified. Cause: Password token is valid but username <username> is invalid"
Gateway managed
PLAIN
Failure
"Authentication failed: credentials for user could not be verified. Cause: Token has expired. Claims: {username=<username>, vcluster=<vcluster>, exp=<timestamp>}"
Gateway managed
PLAIN
Failure
"Authentication failed: username not specified" or "Authentication failed: password not specified"
Gateway managed
PLAIN
Failure
"Authentication failed: credentials for user could not be verified. Cause: Password token is valid for username, but username <username> is not an existing local user."
Gateway managed
OAUTHBEARER
Failure
"{\"status\":\"invalid_token\"}"
Kafka managed
Any
Failure
"SASL Authentication failed."
Kafka managed
Any
Failure
"Gateway can't detect principal from your authorization exchange. Please contact your administrator"
For the Gateway managed with OAUTHBEARER, authentication may also fail if the Kafka client is unable to fetch the token from the configured OAUTH provider. This occurs before reaching Gateway, so audit log event would not be created.
The Kafka protocol describes API keys that represent different kinds of requests that can be made to the broker.On Gateway, you can configure an audit Interceptor to track specific Kafka operations (such as PRODUCE, FETCH, CREATE_TOPICS, DELETE_TOPICS and ALTER_CONFIGS) to elevate audit logging on certain topics as needed.
The ACL admin event tracks Access Control List operations done via Kafka Admin API, such as CREATE_ACLS and DELETE_ACLS requests.ACL operations done via REST API (for Virtual Cluster) are recorded as REST API events.
The authorization failure event records failed attempts to access a resource when ACL permissions deny the operation.ACL permissions are determined by Kafka authorization primitives (i.e. Operation and Resource), resource name, user name, tenant (i.e. Virtual Cluster) name and host.The value of eventData in the authorization failure audit log event depends on the value of SECURITY_MODE configuration.
Security mode
Information in event data
Example event data value
Gateway managed
Kafka authorization primitives
"DENY Operation.WRITE on Resource(name=test-topic, resourceType=TOPIC, patternType=LITERAL) for [Tenant: passthrough, User: test-user, Host: 127.0.0.1]"
Kafka managed
Authorization failure type
"Kafka error 'Topic authorization failed.' when processing 'PRODUCE' request."