Skip to content
CA Spectrum - 9.4.1 to 9.4.4
Documentation powered by DocOps

How to Customize Security String Inheritance

Last update October 13, 2014

Contents

Use the following process to customize security string inheritance:

  1. Add relations for security string roll down.
  2. Define security string roll down overrides for model types.

Relations for Security String Roll Down

CA Spectrum will roll security strings down from the left model to the right model, from the following relations:

  • Application
  • Can_Assign
  • CollectsChassis
  • Collects
  • Contains
  • HASPART
  • Manages
  • Organizes
  • Owns
  • Provides
Note: For specific details about how to use the Model Type Editor to create new model types, see the  Model Type Editor section.

To add new relations that security strings will roll down

  1. Stop the SpectroSERVER if it is running, and verify that there are no other programs running that can access the SpectroSERVER database.
  2. Open the CA Spectrum Control Panel, and click Configure, Model Type Editor.
    The Model Type Editor opens, and the Root model type is set as the current model type. The Root model type is the model type at the highest point in the model type hierarchy.
  3. In the Model Type View, find the Security_Model model type.
  4. Create a new model type, whose base model type is Security_Model.
  5. In the newly created model type, add new attributes of type Relation Handle.
  6. Set the default value of each new attribute to the Relation Handle of the relation that you want security strings to roll down.

Define Security String Roll Down Overrides for Model Types

When joining the security strings of two models for a security string roll down, the AND operator is used by default, unless the model type on the right side of the association has a predefined override.

CA Spectrum provides an override for the Container model type. When rolling down a security string to a model on the right side of a security relation whose model type is derived from Container, the OR operator is used. The only exception to this override is the WA_Link model type, which is derived from the Container model type. When rolling down a security string to a model on the right side of a security relation whose model type is WA_LINK, the AND operator is used.

Define security string roll down overrides in the Model Type Editor.

Note: For specific details about how to use the Model Type Editor and create new model types, see the  Model Type Editor section.

Follow these steps:

  1. Stop the SpectroSERVER if it is running, and verify that there are no other programs running that can access the SpectroSERVER database.
  2. Open the CA Spectrum Control Panel, and click Configure, Model Type Editor.
    The Model Type Editor opens, and the Root model type is set as the current model type. The Root model type is the model type at the highest point in the model type hierarchy.
  3. In the Model Type View, find the Security_Model model type.
  4. Create a new model type, whose base model type is Security_Model.

    Important! Create a new model type rather than modify the Security_Model model type directly since changes to the Security_Model type could be overwritten when installing future CA Spectrum upgrades.
  5. In the newly created model type, take the following steps:
    1. Modify the default value of the Security_String_Mtypes (0x12967) attribute, adding the model types for which you want to define an override.
    2. Modify the default value of the Security_String_Operators (0x12968) attribute, defining the override operators (0 maps to AND, 1 maps to OR) for the model types that were added to the Security_String_Mtypes attribute. The value of instance x in the Security_String_Operators attribute should be the override operator for the model type identified by the value of instance x of the Security_String_Mtypes attribute.
  6. Save your changes and close the Model Type Editor.
Note: Overrides that are defined on model types that are derived from the Security_Model model type take precedence over any overrides that are defined directly on the Security_Model model type.
Was this helpful?

Please log in to post comments.