A messaging client receiving a message from a subscription
The messaging security audit events SECURITY_AUTHN, A SECURITY_AUTHZ, and SECURITY_AUTHN_TERMINATE are produced when a messaging client receives a message from a subscription.
Audit events are produced when a messaging client receives a message from a subscription as follows:
- The messaging client connects to a messaging bus:
- A SECURITY_AUTHN event is produced when the identity of the messaging client connecting to the bus is authenticated.
- A SECURITY_AUTHZ event is produced when the identity of the messaging client is checked for access authority to the bus.
- A SECURITY_AUTHZ event is produced when the identity of the messaging client is checked for authority to receive the message. This check is only performed once per connection session, and the result is cached.
If changes are made to the access rights for the topic, or a new subscription is created that matches an existing topic (either exactly or as a result of a 'wildcard' match), the cache entry for the topic becomes invalid. Another check is made for authority to receive the message, and another SECURITY_AUTHZ event is produced.
- One or more messages are received by the client from a subscription. No audit events are produced.
- When the connection between a messaging client and a messaging bus is terminated, a SECURITY_AUTHN_TERMINATE event is produced.
To record these audit events, we create security event type filters for them.
Related concepts
A messaging client sending a message to a message destination A messaging client receiving a message from a message destination Messaging engines connecting to one another on the same bus Messaging engines connecting to one another on different buses A publisher sending a message to a topic A cell administrator updates a service data object (SDO) repository
Related tasks
Create security auditing event type filters Auditing the service integration security infrastructure