000018769 - How to assign RSA SecurID Web Express users to a group when the group belongs to a site

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000018769
Applies ToRSA SecurID Web Express 1.2
IssueHow to assign RSA SecurID Web Express users to a group when the group belongs to a site
If the group "redsox" were associated with a site (e.g. "boston"), the token request fails. The aceserver log shows the user added and then deleted.
CauseConfigured RSA SecurID Web Express for adding users to an RSA ACE/Server group:

1. Modify the files:
 
RSAWebExpress\JRun\servers\default\rsaswe\WEB-INF\classes\i18n\en_US\
WXUserRequestToken_en_US.properties and WXAdminEditAppReqDetails_en_US.properties


2. Add entries for the groups under or replacing the one that exist for "none":

NOTE: The number increments for additional entries.

tsUserInfoGroupAccess_option0=none
tsUserInfoGroupAccess_optionValue0=none

tsUserInfoGroupAccess_option1=patriots
tsUserInfoGroupAccess_optionValue1=patriots

tsUserInfoGroupAccess_option2=redsox
tsUserInfoGroupAccess_optionValue2=redsox
ResolutionThe entry for a group associated with a site must have the correct syntax which includes the site. This need only be done for the entry that web express uses for the API call to the aceserver. The user display in the pull down can remain just the group name.

tsUserInfoGroupAccess_option2=redsox

tsUserInfoGroupAccess_optionValue2=redsox@boston
Legacy Article IDa29304

Attachments

    Outcomes