+

Search Tips   |   Advanced Search

Puma Store Service

The portal Puma Store Service contains the configuration properties for the Portal User Management (PUMA).

In the WAS console, the portal Puma Store Service is listed as WP PumaStoreService.


Properties for both the Portal User Management and the PUMA SPI

The following properties configure both the Portal User Management and the PUMA SPI:

    store.puma_default.user.fbadefault.filter Default search attribute for users. Usually the same as the Relative Distinguished Name (RDN) attribute of the LDAP. Depending on the environment, it might be a different attribute. The value for this property should correspond to the value of one of the following properties in wkplc.properties, depending on the security configuration:

    • federated.ldap.loginProperties
    • standalone.ldap.loginProperties

    store.puma_default.group.fbadefault.filter Default search attribute for groups. Usually the same as the RDN attribute of the LDAP. Depending on the environment, it might be a different attribute. The value for this property should correspond to the value of one of the following properties in wkplc.properties, depending on the security configuration:

    • federated.ldap.loginProperties
    • standalone.ldap.loginProperties

    store.puma_default.user.base.attributes Attribute subset that portal loads during direct user lookups, for example at Login. Attributes that are not defined in this list are loaded by a separate request to the backend user store.
    store.puma_default.user.minimum.attributes Attribute subset that portal loads during attribute searches for users. Attributes that are not defined in this list are loaded by a separate request to the backend user store.
    store.puma_default.group.minimum.attributes Attribute subset that portal loads during attribute searches for groups. Attributes that are not defined in this list are loaded by a separate request to the backend user store.
    store.puma_default.userManagement.cacheMode Defines whether Puma uses a cache or not. Default is true.
    store.puma_default.logDuplicateKeyExceptions Determine whether the Data Store component writes DuplicateKeyException error messages out to the portal log or not. This does not influence the error handling: With either setting, the exceptions are handled without an error to the portal system.

    true Default. If true or not set, error messages are written to the log. Exceptions are handled without error to the portal.
    false If false, error messages are not written out to the log. Exceptions are handled without error to the portal.


Properties for the Portal User Management only, but not the PUMA SPI

The following properties configure only the Portal User Management, but not the PUMA SPI:

    store.puma_default.puma.commonname The Registration / Edit My Profile portlet can generate the common name (CN) of a user automatically. This property defines how the CN is generated. Define dynamic and static parts. Dynamic parts are added using {X}, where X stands as a reference number to the puma.commonname.X that defines the attribute to place here. Dynamic parts can only be user attributes available and valid. The default is {0} {1}.
    store.puma_default.puma.commonname.parts Number of dynamic parts in the common name.
    store.puma_default.puma.commonname.X The user attribute for dynamic part X. X must be between 0 and puma.commonname.parts -1. The default is puma.commonname.0 = givenname and puma.commonname.1 = sn.


Parent Puma Store and Validation Services