We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
[Security and Access Control][CE] [Security] - Symphony should immediately reflect changes in Active Directory
The current Active Directory behavior in Symphony 7.1 is flawed. Feedback from support is that the expected practice is after a new user or group is added to AD or an existing user is added to an existing group that the cluster should be restarted in order to acquire the changes to Active Directory. This is not correct and is unrepresentative of the manner in which other AD based security models work. For example it is not necessary to restart a file server or SQL server when a user is added into an AD group. Similarly, e-mail systems (such as Lotus Notes) can use AD groups to maintain distribution lists that can be updated without requiring a restart of the server software. The purpose of Symphony AD integration is to enable IT support staff (who do not have knowledge or experience of Symphony) to grant or revoke Symphony access to a user based on that user's membership of groups to which the Symphony administrator has assigned appropriate roles within the cluster. This enables security to be centrally managed by IT support staff in line with most other IT systems. For the design behavior to require a cluster restart following an AD change, this forces the Symphony administrator to be involved in what should be a routine operation. The other principal issue with the design behavior is that a cluster restart is an invasive operation that requires coordinating a period of downtime within the business. For a dynamic organisation where users may need to be added at short notice during a busy time for the cluster this represents a problem, forcing the Symphony administrator to assign roles directly to the user within the cluster. It is clear that Symphony is capable of eventually reflecting AD changes without a cluster restart, however these changes can take anything from a hour to some days to register. This behavior needs to change such that AD changes are reflected in Symphony within seconds and without any additional actions or commands required on the cluster itself.
Do not place IBM confidential, company confidential, or personal information into any field.