Knowledge Base

MCIS: Tokens Associated with User Groups or Access Plans

Article ID: 161905

Article Last Modified on 9/30/2003


APPLIES TO


This article was previously published under Q161905

SUMMARY

The Web templates (ASP files) used to create User Groups and Access Plans can be misleading in regard to the associated token.

MORE INFORMATION

There are two scenarios to consider:
  • When you create a User Group or Access Plan, you are asked to associate a token with the group or plan. (Note: Assign token to a group or plan.) That token is to be assigned to those users who are to have rights to administer that group or plan. The token assigned above does not go into the list of tokens to be associated with the specific group or plan, which then transfers down to members of the group or plan.
  • When you associate a token with a User Group or Access Plan by selecting the token and then associating it with a group or plan, that token will be assigned to all members of the group or plan when they authenticate. (Note: Assign group or plan to a token.) It is using this process by which you add tokens to groups or plans.
For example:
  • Group KidsArea is created and is mapped to a token KidsArea-Token during the creation.
  • In the token management section, token KidsGameZone is added into Group KidsArea by selecting the token and then associating it with the group.
  • Add user Alice into KidsArea group. Alice has rights on KidsGameZone, but not KidsArea-Token.

Keywords: kbinfo KB161905