Pega Platform supports single sign-on. A person or external system that is authenticated by an external application can be authenticated without providing a second user ID and password. The single sign-on feature is implemented through a security token.
An Application ID instance contributes information to the construction and evaluation of security tokens. It provides one password for a group of users who are authenticated externally. It also determines the amount of time allowed between the time a security token is created and the time that the token is evaluated (known as lag time).
Application ID data instances, which support authentication, are different from application rules, which provide the RuleSets and other characteristics of a single application.
For information about implementing single sign-on with a security token, see the PDN article Authentication in PegaRULES Process Commander.
The Data-Admin-AppID class contains Application ID data instances. They are part of the Security category.
When you save an Application ID data instance, if the Associated RuleSet is [none], the system completes this field with a RuleSet from the current application. This association assists with application packaging. You can update the associated RuleSet using the field in the upper right corner of the form. See Identifying parts of rule and data forms.
If there is no RuleSet associated with the data instance (for example, for existing instances not previously associated with a RuleSet), the Associated RuleSet displays [none].