Show Table of Contents
1.4. Using Security Elements and Attributes
- The <component><service> and <component><reference> security Attribute
- Component Services and Component References can specify an optional sy:security attribute. This attribute points to a named <security> element in the domain section. If not defined, use the default value.
- The callbackHandler Attribute
- This is an optional attribute. If not specified, use the default value of
org.switchyard.security.callback.NamePasswordCallbackHandler. - The name Attribute
- This is an optional attribute. If not specified, use the default value of default. Component Services and Component References point to this name.
- The rolesAllowed Attribute
- This is an optional attribute. If specified, and if a Service has an authorization security policy requirement, the authenticated user must be in one of the roles listed.
- The runAs Attribute
- This is an optional attribute. If specified, add the value of this attribute as a role to the authenticated user.
- The securityDomain Attribute
- This is an optional attribute. If not specified, use the default value.
- The <properties> and <property> Elements
- A <security> element can optionally specify a <properties> element, which can optionally specify zero to many <property> elements. Each <property> element has two required attributes: name and value. The list of specified name/value properties are made available to the SwitchYard Security configuration, as well as the configured callbackHandler.
- The <securities> Element
- This is an optional element. Contains any number of <security> elements. If not defined, use the default security configuration.
- The <security> Element
- This is an optional element. If not specified, the callbackHandler, name, and securityDomain attributes will fallback to their default values.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.