WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Required security token settings

Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.

To view this administrative console page, click Service integration > Web services > WS-Security configurations > [Content Pane] v1-outbound-config-name > [Response consumer] Required Security Token > [Content Pane] security-token-name.

Configuration tab

Configuration properties for this object. These property values are preserved even if the run-time environment is stopped then restarted. Changing these property values typically has no effect until the run-time environment is restarted; for example, by stopping then restarting an application server. See the information center task descriptions for information about how to apply configuration changes to the run-time environment.

General properties

Name

The name of the security token.

Required Yes
Data type Text

URI

Specifies the namespace URI of the security token.

Required No
Data type Text

Local name

Specifies the local name of the security token.

Required Yes
Data type Text

Usage

Indicates the assertion of the required security token constraint.

Required Yes
Data type Selection list
Range
Optional
Both messages that meet or do not meet the required integrity constraint are accepted.

Required
The required integrity constraint must be met by the incoming message.


Reference topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\sibuswssecurity\ResConRequiredSecurityToken_DetailForm.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)