Start of change
WebSphere Message Brokers
File: ap04080_
Writer: Stephanie J Strugnell

Concept topic

This build: July 31, 2007 21:34:47

Security exception processing

Security exceptions are processed in a different way to other errors on the input node. Whilst an error is usually caught on the input node and flowed down the catch terminal for error processing, security exceptions are not processed in the same way. By default the broker does not allow security exceptions to be caught within the flow, and backs the message out or returns an error (in the case of HTTP). If you have designed the flow to be in a secure area and you want to explicitly perform processing of security exceptions, you can select “Treat Security Exceptions as normal exceptions” on the input nodes. This causes security exceptions to flow like any other exception in the flow.

Related concepts
Identity
Authentication
Identity mapping
Authorization
Identity propagation
Security profiles
Related tasks
Configuring identity
Configuring authentication
Configuring identity mapping
Configuring a security profile
Configuring authorization
Configuring a message flow for identity propagation
Setting up message flow security
Related reference
mqsicreateconfigurableservice command
mqsideleteconfigurableservice command
mqsichangeproperties command
mqsireportproperties command
MQInput node
HTTPInput node
HTTPRequest node
MQOutput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:47

ap04080_ This topic's URL is:
End of change