![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You can define different security domains where each domain defines a different set of security-related behaviors. You specify security settings that define the security behavior for a security domain in a security policy file. See Security Policy Files for more information on security policy files.If you want to apply the same security settings to more than one metaspace, you can associate the same security domain with multiple metaspaces. However, only one security domain can be associated with each metaspace. See Metaspace Access List for more information on associating metaspaces with security domains.To utilize security within a metaspace, one or more nodes in the metaspace are initialized as a security domain controller for the metaspace. A security domain controller enforces the security domain's defined behavior for a metaspace. A security domain controller can be the manager of a metaspace or just a member of a metaspace. See Security Domain Controllers for more informationFigure 2 shows the two node types in the TIBCO ActiveSpaces security architecture.
• Security Domain Controllers TIBCO ActiveSpaces nodes that are dedicated to enforcing a security domain's defined security behavior for a metaspace associated with the security domain. Security domain controllers are the only discovery nodes in a metaspace.
• Security Domain Requestors Nodes that require access to the data in the data grid, such as a seeder or a leech, and which need to be authorized by a controller. Requesters can never be used a discovery nodes.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |