Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Automatically Added Occasional Users from LDAP get Regular access type by default
Automatically Added Occasional Users from LDAP get Regular access type by default LDAP users should be created in SBM with occasional access type when you set the Default SBM User Group for new users to a group with occasional access type but users are being created with regular access type instead.
CMS-XML Privileges incorrect after user added to Occasional Group
The only workaround is to add the user to a Regular User group, or remove their ID from the group for Occasional Users .
CMS-XML Logging user added to group is written differently to TS_AdminChanges whether one uses the Web Admin or the System Admin.
Logging user added to group is written differently to TS_AdminChanges whether one uses the web admin or the System Admin Tool. For example if a user is associated with 10 groups and is then added to an 11th, the action as logged from the System Admin tool will only add one line to the TS_AdminChanges. Whereas if the action is carried out from the Web Admin, lines are logged for removing the user from all 10 groups and then adding them and the new group again.
CMS-XML No warning message of losing changes when adding users to a group and searching for other users
When in Groups, memberships and search for a user, check box the user to add them to the group, then search for another name, there is no warning that the changes are not saved. The user can continue searching/ adding users only to find out at the end that none were saved. The save icon needs to be used on each and every user search.
CMS-XML Changing group to managed administrator does not remove regular users
If a group is changed from Regular User access to Managed Administrator access and granted the Remote Administration system privilege, then all users currently in that group who only have Regular User access become Global Administrators. This makes it very easy to accidentally grant global admin privileges to users without realizing it.
CMS-XML Extra group membership removed in web administrator
To work around this issue, the group membership that has the TS_ID in the TS_MEMBERS table that matches the TS_ID of the group in the TS_GROUPS table can be removed and re- added for the user from the Mashup Administrator.
CMS-XML Handling User and Group Selections in New Web-based Administrator
IMPORTANT: This is working as designed with the new Application Administrator. The fix for this is the adding of a warning message when user tries to remove a selection
CMS-XML : mail events : warning the user/group ... has already been subscribed to this not
2) the group or the user has been successfully added. Then when redisplaying the dialog box to add or remove subscriber then the user or group previously added still appear in the "Available group " list rather than to be displayed in list " Groups to subscribe"
CMS-XML DimCM - Error: You do not have the Manage Users and Group Definitions privilege(ADMIN_USERMAN) to perform this operation
3. Under Administrative Privileges, select 'Manager Users and Groups' privilege. 4. Check to see if you are in a group that has an Explicit Deny specified in addition to the default Explicit Grant rule for the ADMIN group , and remove the Explicit Deny. 5. This will restore your Admin privileges.
CMS-XML User LDAP update does not do anything
<p>When updating user from LDAP using the user update tool in the Web Administrator the process seems to finish but no user are updated.</p>
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs