Access Controls

Showing 14 of 5881

Baselines cannot be accessed after replacing user accounts in RDS.

A customer has replaced local users accounts with RDS authentication whereby all old locals accounts have been removed from database. This means that now no users can access baselines because a baseline is immutable, therefore you cannot modify th...

2 days ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Submitted

5 VOTE

Make the 'Add Access' dialogue accept the selection and acting upon of multiple Groups/Users at once

This provides the ability to add/edit/remove several groups/users to/from the Item at the time and helps a lot (!) for many access right operations on the item (object, module, project, folder). Currently the dialogue only allows selecting and act...

11 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

3 VOTE

To the AddAccess dialogue add the ability to filter with position- and case-sensitivity on (group or user) names to reduce the (result) list of groups/users displayed.

We request the addition of a filter feature: The user enters a character into the filter-field and the list is automatically filtered according to the type character string. The filtering is position- and case-sensitive. See screenshots

11 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

2 VOTE

Support OAuth 2 for OSLC integrations

OAuth 1.0a as supported currently in DOORS 9 is deprecated according to https://oauth.net/core/1.0a/ and has been replaced by RFC 6749 (OAuth 2.0). In order to integrate between DOORS 9 and other modern OSLC applications, DOORS 9 shall support the...

10 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

2 VOTE

In the AddAccess dialogue, do not display user names together with group names by default.

Large organisations with hundreds or thousands of users and groups often manage access controls through groups. Displaying all the users together with all the groups in the 'Add Access' dialogue by default, is often not necessary and creates consi...

11 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

2 VOTE

Make the 'Add Access' dialogue window resizeable to allow displaying Group or User names that are longer than the width of the default dialogue window size.

Items (objects, modules, projects, folders and others) in DOORS 9 client, have a properties - access panel, which has an 'add access' button. The 'Add Access' dialogue behind it, is of fixed size, which can lead to overly long group and usernames ...

11 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

3 VOTE

Similar to "Disable Logins" database login property, provide a "Disable Editing" to override all ordinary access controls when activated, until deactivated, when previous ordinary access controls are taking effect again.

Various tasks in the domain of administering a DOORS 9 database (server) may require to switch a database to read-only outside the ordinary access control management workflow. Be it to freeze a specific state of the database / projects / modules o...

over 1 year ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 1 Future consideration

4 VOTE

Terminate user sessions after maximum 24 hours on inactivity to comply with CMMC AC.3.019

CMMC AC.3.019 requires terminating user sessions after a defined period: Validate that:1. User sessions automatically terminated after a maximum of 24 hours of inactivity2. After user sessions are terminated due to inactivity, the application is c...

about 2 years ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

4 VOTE

Add client version logging to login_history.txt

add logging to login_history.txt to record the client version

over 3 years ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 1 Not under consideration

1 VOTE

How to prevent users from changing the Default Module View

Currently many users create and save their own views as the Default view of the module. There is no way to lock down the Default view for the module and to prevent users from saving their own views as the Default view for everyone.

10 months ago in IBM Engineering - Requirements Management DOORS/DOORS Web Access / Access Controls 0 Future consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Access Controls

Baselines cannot be accessed after replacing user accounts in RDS.

Make the 'Add Access' dialogue accept the selection and acting upon of multiple Groups/Users at once

To the AddAccess dialogue add the ability to filter with position- and case-sensitivity on (group or user) names to reduce the (result) list of groups/users displayed.

Support OAuth 2 for OSLC integrations

In the AddAccess dialogue, do not display user names together with group names by default.

Make the 'Add Access' dialogue window resizeable to allow displaying Group or User names that are longer than the width of the default dialogue window size.

Similar to "Disable Logins" database login property, provide a "Disable Editing" to override all ordinary access controls when activated, until deactivated, when previous ordinary access controls are taking effect again.

Terminate user sessions after maximum 24 hours on inactivity to comply with CMMC AC.3.019

Add client version logging to login_history.txt

How to prevent users from changing the Default Module View

Please enter your email address

FILTER BY CATEGORY