Bugzilla – Bug 654671
iManager does not respect preferences for Initial View after installing IDM 4.0 plugins.
Last modified: 2012-04-28 07:28:33 UTC
SLES 10 SP3 iManager 2.7.3 FTF 4 A fairly new and clean install of iManager on my server is not accepting my preference for an initial view of the Roles and Tasks section of iManager. After installing the IDM 4.0 plugins they are now the default (first button on top and they show up by default when logging in). I went to the Preferences section and set Roles and Tasks to be the first view, saved, then logged out and in and nothing has changed. Tried restarted Tomcat and still didn't help. Tried setting the initial view to the Object view, which also does not work. I do not know if this worked before adding the IDM plugins or if something else may be wrong with my system but I'm not getting any errors... just no following of my preference (which is being saved if I go back and look at preferences again). I do know that my iMan 2.7.3 FTF 4 Workstation version does properly follow preferences before adding my IDM 4.0 plugins. After adding the IDM 4.0 plugins the preferences appear to be ignored in Workstation as well. Expected Results: Follow preferences. Actual Results: Preferences ignored. I am reporting this against iManager (vs. IDM) because this functionality is (theoretically) plugin-agnostic. I imagine something is wrong with the IDM 4.0 plugins causing the problem that can be worked through by collaborating with engineers from both groups.
top-issues: requesting CCB review and updates on this bug.
This has come up in the public forums as of today: http://forums.novell.com/showthread.php?t=432493
Hi Aaron Burgemeister, The fix for this bug is incorporated as part of the fix for the Bug 603660(iManager should provide as a default view of IDM page).In the latest release imanager274 FTF2 this functionality is working fine. Mentioned below are different scenarios of Imanager PREFERENCES. scenarios 1:- 1-> If IDM engine as well as IDM plug-in is installed . 2-> Login into iManager as admin . Expected Result - iManager home page should open as a default page of IDM . scenarios 2:- 1-> If IDM engine or IDM plug-in is not installed in the box . 2-> Login into iManager as admin . Expected Result -iManager home page should open as a default page of Roles & tasks . scenarios 3:- 1-> If IDM engine is not installed and IDM plug-in is installed in the box . 2-> Login into iManager as admin . Expected Result -iManager home page should open as a default page of Roles & tasks . The user can still use iManager preferences to change the view according to there choice. Note : If the IDM engine is not installed then IDM page will not be displayed as the initial page, even if we set IDM page as the default page in the preferences. I have tested these scenarios in OES,SLES10SP3 & SLES11 with and without IDM engine(server).
Scenario #1 is wrong and is why this bug was created. A default is fine (if documented, which it is not as far as I can tell), but not being able to change it is unacceptable.
Hi Aaron, As per comment #5 and #7, this issue seem to be resolved in latest iManager version. Currently iManager 2.7.4 FTF2 is under FA testing. Following is the build location: http://164.99.147.117/artifacts/iManager-deliver/iMan27SP4_FTF2/iManager-deliver~iMan27SP4_FTF2_20110218_112713.zip Request you to try this latest iManager patch and share your observation. Thanks, Kedar
I do not have a system that I can risk breaking right now. If QA has the reported issue and finds that FTF 2 resolves it then that's good enough for me.
Hi Kedar, I have cross verified preferences setting against latest iManager 274 FTF2. My findings are below :: 1. IDM engine + IDM plug ins -> iManager framework is taking care of preferences setting as per the user input. 2.Non IDM engine + IDM plug ins -> iManager framework is taking care of default setting as expected . But, it is not taking care of IDM page , even user hit the set initial view as IDM page . 3.If IDM engine or IDM plug-in is not installed in the box . Login into iManager as admin . By default Roles and tasks page will display. Eventually , we are unable to hit this issue in latest iManager 274 FTF2 . Thanks Anil
Thanks Anil for sharing your observations. Aaron, based on comment #11, please update the bug as DSLA_SOLUTION_PROVIDED. Regards, Kedar
I completely disagree with this resolution. Bug# 603660 (which was only an enhancement, and as far as I can tell had no customer basis) changes a global default in a way that is unnecessary. Users have, as long as IDM has had its own section of iManager, been able to set the default to the IDM view for their users; this "enhancement" now forces all users to use the new view, even if they do not use IDM. IDM is a great product, but not everybody in an organization has a need for it any more than every user in an organization has a need for the iPrint functionality, or the RBS functionality, or any other functionality. iManager is built around the model of roles and now we have forced one role on everybody unless everybody (except those in one single role) changes their defaults rather than letting those with a given role (the few) change their defaults as they could do all along. This functionality should be reverted so that those who want to change their default can, and those who do not are not given extra work to get back to the correct state.
Let me bring the attention back to the issue reported in this bug. As i understand, the reported issue is as follows: After installing IDM plugins, the default page for iManager was made to be IDM page. Now when user modified this default page to be Roles and Tasks, it was not effected (still IDM page was displayed as default). Both development and test engineers have confirmed in the comments above that this issue is resolved with iManager 2.7.4 FTF2. Aaron, would like to know more details about the scenario you are refering related to the reported issue, which is not resolved?
The default should never be changed. IDM is one small part of iManager's functionality. A customer is unlikely to ever install a separate server just for iManager for IDM. The eDirectory team has, for years, discouraged multiple iManager instances (why have them?) and so the change to have IDM be the default (even if configurable in another way) does not make sense and should not be present. There does not appear to be any kind of customer-basis for this change and so far we already have bugs because of the change not being expected (and in this case, not being reversible).
info provided
IMO comment #16 is a deviation from the reported issue while filing the bug. Considering that we need to look at bug 603660 and this one together, I would like to hear from IDM CCB for their recommendation. Hence including appropriate stakeholders in CC and marking it for CCB review. Once IDM CCB provides their recommendation, i would suggest it to be discussed in iManager CCB and conclude.
I agree with Aaron. The opinion of WWS should be heavily weighted.
NEEDINFO to engineering is not valid on a DSLA bug as it incorrectly manipulates the DSLA metric.
The enhancement requested in bug#603663 was to simplify user experience in IDM environment. When user connects to IDM server and if the initial view preference is not set, iManager should display IDM Administration page. If user connects non-IDM server, iManager will not show IDM Administration as default view. If the fix is not implemented this way, we should re-open bug#603663. If the issue reported in this bug is already fixed. We can mark this bug resolved/fixed.
The fix is implemented in this way: > When user connects to IDM server and if the initial view preference is not set, iManager will display IDM Administration page as default page. > If user connects non-IDM server, by default Roles and tasks page will display. Thanks&Regards, M.Nagaprasad.
I understand how this could be implemented, and that it was perhaps done to ease the user experience for one very small group of IDM administrators, but iManager's purpose is not entirely the result of IDM, even in environments where iManager is on the IDM machine physically. Being one of dozens of plugins and presuming that our view should be the default over the regular Roles and Tasks view (which allows access to all plugins) is presumptuous; if an administrator wants to change, they can. If they don't know what they're doing, they should be going through the docs anyway. In any case making this the default view without any intervention/prompt does not have any merit when considering the available alternatives. IDM does not live in a vacuum.
Other relevant points: For customers who are new, likely the only demographic where this "enhancement" makes sense, Designer should be their primary tool for everything. Since IDM comes with Designer and Designer can do just about everything IDM-related (where iManager definitely cannot as much functionality is only in Designer) that is the more-logical place to spend effort entering enhancements for usability. Designer also allows offline use and seems to be the direction we are continuing to push for IDM functionality instead of devoting a lot of work to iManager which, afaik, doesn't even have a roadmap into the future (we've already pushed out its lifecycle duration at least once, as a result). The other place this could make sense is using the Integrated Installer to build a completely new environment/tree all on one system; however, the Integrated Installer is now only for testing purposes so that example doesn't hold up either.
So, from the below discussions and from what Aaron has been talking about, the following two requirements emanate a. When iManager is installed w/o IDM, do not make the default view as IDM, leave it to the administrators thru preferences. This goes against how it was discussed and designed in IDM 4. I might agree with Aaron here, however I am open to reviewing and re-discussing the design. b. In an IDM4 env, where the default view is IDM, administrators are unable to reset it to the default (Roles and tasks view). Kedar says that this is fixed in iManager 274 FTF2. Comment #11 from Anil Kumar Pal doesn't clearly indicate if this is working in iManager 274 FTF2. Hence, I would like him to comment again. So, b) can be a defect if it doesn't work against iManager 274FTF2 and a) is a design level discussion. -Krishnan
I have tested and verified this issue against iManager 273 FTF4 workstation as Aaron did and also on iManager 274 server (shipping with IDM 4.0). Below are my findings. 1. iManager 274 server with IDM 4.0 installed using IDM wrapper installer -> Login into iManager -> The default page is the IDM Administration page -> Change the preferences default view to "Roles and Tasks" -> Logout and login again -> The default page is now changed to 'Roles and Tasks' 2. Workstation iManager 273 FTF4 (As per Aaron first comment) -> Login using iManager to target IDM 4 server. -> The default page is the IDM Administration page -> Change the preferences default view to "Roles and Tasks" -> Logout and login again -> The default page is again the IDM Administration page. - not changing to Roles and Tasks view (This is exactly what Aaron is talking about). 3. Upgrade Workstation iManager 273 FTF4 to 274. -> Login using iManager to target IDM 4 server. -> The default page is the IDM Administration page -> Change the preferences default view to "Roles and Tasks" -> Logout and login again -> The default page is now changed to 'Roles and Tasks' Thus, it is easy to conclude that iManager 274 behaves correctly and honors the change in preferences. Hence, I feel that it is working as per design and correctly with iManager 274 (FTF not required).
Based on inputs in comment #26, this bug is not reproducible with iManager 2.7.4. Hence marking it for needinfo to reporter to confirm and update the bug accordingly. Also, it might be advisable to re-open the enhancement #603660, as there is a opinion mentioned that this enhancement may cause inconvenience to a significant portion of iManager users.
Comment #26 states the the problem (IDM plugins' incorrect changing of default views) is still happening and requiring for things to be set back to as they were with all previous versions of iManager. There is nothing to test until that is fixed and the default view is left as it should be on Roles and Tasks.
Comment #26 clearly mentions that the said issue which was reported on iManager 2.7.3.x is resolved with iManager 2.7.4. Following is the summary observations from comment #26: "Thus, it is easy to conclude that iManager 274 behaves correctly and honors the change in preferences. Hence, I feel that it is working as per design and correctly with iManager 274" Marking it for Needinfo to reporter to confirm if the reported issue is reproducible with iManager 2.7.4. If yes, request him to share the setup for the same for further analysis.
iManager 2.7.4 does not change anything. The default view is still set to the IDM plugins is there was no preference previously set. Worded another way, if an administrator previously did not see a need to change the behavior (meaning Roles & Tasks was correct for them) we now change things on them without permission. It appears that the original bug report was a bit short-sighted. I focused on the inability to change things back but also reported it on what is likely an unsupported setup (2.7.3). Since it appears no coding has been done specifically for this bug report we still have things to fix. If the title of this bug should be changed, so be it, but in the end the original problem of the preference being changed still exists with 2.7.4. 2.7.4, which was out at the time of this bug report, does nothing to fix the problem of the default changing. In the end that may not be a bug with iManager itself as much as the IDM plugins though I believe the same team writes both today. Assign to the correct product and engineer as needed.
I can understand where Aaron is coming from. He probably has a valid point. However, when IDM 4.0 was designed, the architects decided to make the IDM page as default and they probably had a good reason to do so. At this point, I would like Jaimon or Mangal to comment and recommend further action.
Whatever the reason. The field has rejected it.
(In reply to comment #28) > Comment #26 states the the problem (IDM plugins' incorrect changing of default > views) is still happening and requiring for things to be set back to as they > were with all previous versions of iManager. There is nothing to test until > that is fixed and the default view is left as it should be on Roles and Tasks. If iManager 2.7.4 connects to an IDM server, the default view will be IDM Administration page. This is as per requirement of IDM4.0 and comment#26 indicates that its working as designed. Administrator will have an option to set the preferences to any other views. Comment#26 indicates that the same is possible even now. So I don't see any fix required for this defect and request product team to close the defect.
Jaimon, When you install the IDM plugins it ALWAYS shows the IDM view as the default regardless of where iManager is connecting, EVEN IF IDM IS NOT INSTALLED IN THE TREE. For years Novell has recommended customers to have only one or two (2nd for redundancy) iManager server to provide administration capabilities to their systems. I've worked with many major accounts where their admin & helpdesk team accessed a single iManager to manage multiple trees with multiple servers. The fact the IDM plugins are needed to manage a single server in a few of those trees is no reason to change the default view in iManager for everyone. Feedback from internal and external lists, customers and NTS shows that the design is faulty. If IDM were an appliance with its own iManager then having the IDM view be the default view would make sense. Since IDM is not an appliance and the plugins can be installed in any iManager, having the IDM view be the default view is a defect. Not a code defect (since its by design), but a PRODUCT DESIGN defect that needs to be corrected both on the product design and, by extension, in the code. Updating the defect is taking us nowhere. We need a conference call with all stakeholders. Too much time has been wasted with back and forth arguments in the bug itself. Cheers, -Fernando
(In reply to comment #34) >When you install the IDM plugins it ALWAYS shows the IDM view as the default >regardless of where iManager is connecting, EVEN IF IDM IS NOT INSTALLED IN THE TREE. Anil, In Comment #26, all the backend servers are IDM servers. Can you try against a setup were there is no IDM and comment?
With IDM-plugin installed and chosen as default view, when you login into a tree with no IDM, the default page view is 'Roles and Tasks'. In my opinion, this is working as expected .
Jaimon, Anil has provided his observations in comment #37. do we need any other inputs to conclude on this? Thanks, Kedar
I have yet to find anything stating that we are resolving this correctly by putting the defaults back to how they have always been previously. It appears that in environments that are not created by the Integrated Installer we are still overriding all of iMangaer's other options and setting the default to be the IDM plugins.
just duplicated the behavior described by Jaimon in my lab, and if iManager goes to a server that does not have IDM installed/configured then it shows the regular view. I still believe that the IDM iManager plugins should never default to the IDM view, but don't feel as strongly since this happens on a subset of the scenarios I originaly believed it did.