iManager 2.7.6 patch 1 issue with Identity Manager Overview


Was updating a 2.7.5 install to 2.7.6 and applying Patch 1. My
finished installation seemd ok, except one issue when I try to utilize
the "Identity Manager Overview" screen, I am presented with the screen
to select my search base, and click on the "Driver Sets" or "Libraries"
tab. When I click on either, nothing happens.... and when I then try
to do any other iManager function, it takes me to the authentication
screen. Basically, it is as if "Drivers Sets" was programed for
"Logout" !!

I have removed iManager completely and then reinstalled 2.7.6 from
scratch, and applied Patch 1. I have deleted and created a new RBS
collection, and nothing seems to fix it.

Any thoughts as to what this could be ?

Thanks!


--
mmiltenberger
------------------------------------------------------------------------
mmiltenberger's Profile: https://forums.netiq.com/member.php?userid=201
View this thread: https://forums.netiq.com/showthread.php?t=47720

Tags:


  • Just to validate, I again went and removed iManager completely, deleted
    subdirs, etc. Installed 2.7.6 from scratch, and all iManager
    functionality is there...even the Identity Manager Overview works just
    fine. So I then apply Patch 1, and it is indeed broken again as
    described below.


    mmiltenberger;229389 Wrote:
    > Was updating a 2.7.5 install to 2.7.6 and applying Patch 1. My
    > finished installation seemd ok, except one issue when I try to utilize
    > the "Identity Manager Overview" screen, I am presented with the screen
    > to select my search base, and click on the "Driver Sets" or "Libraries"
    > tab. When I click on either, nothing happens.... and when I then try
    > to do any other iManager function, it takes me to the authentication
    > screen. Basically, it is as if "Drivers Sets" was programed for
    > "Logout" !!
    >
    > I have removed iManager completely and then reinstalled 2.7.6 from
    > scratch, and applied Patch 1. I have deleted and created a new RBS
    > collection, and nothing seems to fix it.
    >
    > Any thoughts as to what this could be ?
    >
    > Thanks!



    --
    mmiltenberger
    ------------------------------------------------------------------------
    mmiltenberger's Profile: https://forums.netiq.com/member.php?userid=201
    View this thread: https://forums.netiq.com/showthread.php?t=47720

  • Out of curiosity was the original install iMan 2.7 SP6 or was it upgraded
    from something previously? I just patched my 2.7 SP5 server system to 2.7
    SP6, and then to Patch 1, and am not seeing what you are reporting. As my
    system has been around for a while it's possible some combination of
    settings has affected it positively to prevent the issue, but I'm not sure
    what those would be. I assume your systems are Linux as mine are, but
    maybe that's a difference.

    I also installed a new 2.7 SP7 iManager Workstation instance and then
    patched it; so far no issues that I can tell related to what you have
    reported.

    Good luck.
  • ab,

    > Out of curiosity was the original install iMan 2.7 SP6 or was it upgraded
    > from something previously? I just patched my 2.7 SP5 server system to 2.7
    > SP6, and then to Patch 1, and am not seeing what you are reporting. As my
    > system has been around for a while it's possible some combination of
    > settings has affected it positively to prevent the issue, but I'm not sure
    > what those would be. I assume your systems are Linux as mine are, but
    > maybe that's a difference.
    >


    Please excuse my jumping in, but is the patch to take 2.7.5 to 2.7.6
    available publicly? I'm looking at Novell's Patch Finder right now and
    I see no patches at all for iManager 2.7.5.


    Thanks,




  • Argh... I did the same thing last night while trying to test this.

    For a regular server-based install go to the download page (not Patch
    Finder... I know, I know... it's a quirky nuance) and then look at
    iManager downloads. The iManager 2.7 SP6 download is a full installer, so
    it's on the main download page instead of the patch page. When you run
    it, though, it will (or did for me on SLES) detect iManager, confirm with
    you that it's an upgrade, and then go through it.

    Good luck.
  • ab,

    > Argh... I did the same thing last night while trying to test this.
    >
    > For a regular server-based install go to the download page (not Patch
    > Finder... I know, I know... it's a quirky nuance) and then look at
    > iManager downloads. The iManager 2.7 SP6 download is a full installer, so
    > it's on the main download page instead of the patch page. When you run
    > it, though, it will (or did for me on SLES) detect iManager, confirm with
    > you that it's an upgrade, and then go through it.
    >


    After I posted, I wondered if in fact the 2.7.6 install would perform an
    upgrade if it could. Since my servers are RHEL not SLES, I'll try it on
    a server that's not in production use.


    Thanks




  • ab;229399 Wrote:
    > Out of curiosity was the original install iMan 2.7 SP6 or was it
    > upgraded
    > from something previously? I just patched my 2.7 SP5 server system to
    > 2.7
    > SP6, and then to Patch 1, and am not seeing what you are reporting. As
    > my
    > system has been around for a while it's possible some combination of
    > settings has affected it positively to prevent the issue, but I'm not
    > sure
    > what those would be. I assume your systems are Linux as mine are, but
    > maybe that's a difference.
    >
    > I also installed a new 2.7 SP7 iManager Workstation instance and then
    > patched it; so far no issues that I can tell related to what you have
    > reported.
    >
    > Good luck.



    First time was an upgrade from 2.7.5 to 2.7.6, then applied Patch 1.
    Once the problem was recognized, I did an uninstall of 2.7.6 and deleted
    the /var/opt/novell/iManager, var/opt/novell/tomcat7,
    /opt/novell/iManager, and /opt/novell/tomcat7 directories, then
    installed from scratch, 2.7.6. Which works, until Patch 1 is applied.

    Now, I have went to another box (and yes, these are SLES 11, x86-64
    instances with eDir 8.8.7) which should be identitical installation to
    first server; 2.7.5 to start with. Start the 2.7.6 installer, and am
    given the "Upgrade" option and continue on. After upgrade to 2.7.6,
    everything works...i.e. the Identity Manager Overview and selecting
    Driver Sets tab, and desired driver set. Now installing
    iManager276_Patch1_Linux.tar. Now trying iManager, and the Identity
    Manager Overview, and I get the same thing.... it basically does
    nothing, and when I try anything else, I am prompted for authentication,
    just like the original problem reported.


    --
    mmiltenberger
    ------------------------------------------------------------------------
    mmiltenberger's Profile: https://forums.netiq.com/member.php?userid=201
    View this thread: https://forums.netiq.com/showthread.php?t=47720

  • We had the same problem...
    Simply clearing the browser cache resolved it, see TID 7012336.

    Hans-Dieter