Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
PDF SBM Application Administrator Features
Users , Groups , and Role ... settings for multiple user and group accounts. ... and privileges for users and groups . ... when working with group membership. ... tables: ▪ Adding and deleting field selections for User , Multi- User , and Multi- Group fields. ... default values for User , Single Relational ... , Multi- Group , Multi Relational ... and Multi- User fields. ... selections for dependent User , Multi- User , or Multi- Group fields are established in the independent User and Single Selection ...
PDF SolutionsBusinessManager 11.5WebApplication SecurityAssessment
... ), all user access goes through ... SBM Configurator provides several options for identity providers, such as internal user database, Windows domain, LDAP , or other third-party providers. ... In addition, SBM provides controls for managing the idle timeout of session token lifetimes for security tokens. ... SBM Application Administrator provides administrators with the ability to set user permissions at role, group , and individual levels, giving administrators the ability to follow the principal of least privilege—al- lowing users to have the least possible authority necessary to do their job. ... LDAP injection
PDF Serena Business Manager 11.2 Web Application Security Assessment
... ), all user access goes through ... ... such as internal user database, Windows domain, LDAP , or other ... ... managing the idle timeout of session token ... ... ability to set user permissions at role, group , and individual ... privilege—allowing users to have the ... • External/out-of-band interaction • HTTP header injection • XML/SOAP injection • LDAP injection • Cross-site request forgery • Open redirection • Header manipulation • Server-level issues
PDF Serena Business Manager 11.1 Web Application Security Assessment
... ), all user access goes through ... ... such as internal user database, Windows domain, LDAP , or other ... ... managing the idle timeout of session token ... ... ability to set user permissions at role, group , and individual ... privilege—allowing users to have the ... • External/out-of-band interaction • HTTP header injection • XML/SOAP injection • LDAP injection • Cross-site request forgery • Open redirection • Header manipulation • Server-level issues
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.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs