[OPENIDM-10969] Backport OPENIDM-10948: OpenerHandler require does not work with Internet Explorer Created: 18/May/18  Updated: 26/Nov/18  Resolved: 26/Nov/18

Status: Closed
Project: OpenIDM
Component/s: Module - Web UI
Affects Version/s: OpenIDM 5.0.0, OpenIDM 5.5.0, OpenIDM 6.0.0
Fix Version/s: 6.0.0.1

Type: Bug Priority: Major
Reporter: Matthias Grabiak Assignee: Mark Offutt [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: Sustaining
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File idm-am.mp4     File idm5511FullStackSession-2018-08-14_19.06.30.mp4    
Issue Links:
Backport
is a backport of OPENIDM-10948 OpenerHandler require does not work w... Closed
Target Version/s:
Verified Version/s:
Story Points: 1
Support Ticket IDs:

 Description   

This affects the call

ServiceInvokerTarget = (opener || window).require("org/forgerock/commons/ui/common/main/ServiceInvoker"),

in UserModel.js when reauthentication occurs with the login window in a popup, resulting in exceptions in Internet Explorer with the ugly result that an empty popup window remains on screen. The following works correctly:

ServiceInvokerTarget = require("org/forgerock/commons/ui/common/main/ServiceInvoker"),



 Comments   
Comment by Jakub Janoska [X] (Inactive) [ 31/Jul/18 ]

On OpenIDM 6.0.0 the behavior is a little bit different. I used updated steps to reproduce from OPENIDM-10948, also attached screencast.

  1. Set up the full stack sample
  2. Log in as a regular user, AM will validate and return control to IDM, like the dashboard
  3. Duplicate the tab
  4. One the second tab log out
  5. Go back to the first tab and try switching to the Profile View
  6. Click on the sign in button that appears
  7. [diff] New window is open
  8. Enter credentials and press the login button (in new window)
  9. [diff] Dashboard is open in new window. 

It works on the all browsers the same way and from this reason I am closing this issue as resolved for 6.0.0.1. 

 Verified on OpenIDM version "6.0.0.1-M2" (build: 20180727121825, revision: c153d8e) jenkins-openidm-release-sustaining%2F6.0.x-20 and OpenAM 6.0.0.3 for backstage.

Tested on these browsers&OS:

Windows 10 macOS Siera Ubuntu 16.04
FF 61 FF 58  FF 61
Chrome 68 Chrome 67 Chrome 67
Edge 42 Safari 10  
IE 11    

 

Comment by Jakub Janoska [X] (Inactive) [ 31/Jul/18 ]

Reopening for 5.5.1.1. and 5.0.1.1.

Comment by Jakub Janoska [X] (Inactive) [ 14/Aug/18 ]

 

Matthias Grabiak, Mark Offutt [X] On OpenIDM 5.5.1.1 I am seeing problem with "Session Expired" after the fix. This problem is not reproducible on OpenIDM 5.5.0 or OpenIDM 5.5.1. Please look at attached video with affected behavior or on the steps to reproduce below.

Steps to reproduce:

  1. Set up the full stack sample
  2. Log in as a regular user, AM will validate and return control to IDM, like the dashboard
  3. Duplicate the tab
  4. One the second tab log out
  5. Go back to the first tab and try switching to the Profile View
  6. Click on the sign in button that appears
  7. In new pop up enter credentials and log in (pop up is closed and the browser displays the Profile page)
  8. Try to navigate on some link, for example "account Controls".

Expected result: Account controls is correctly opened

Actual result: Pop-up with Session Expired is displayed. (session expired happens every second navigation in self-service UI).

 

Issue is reproducible on OpenIDM version "5.5.1.1-SNAPSHOT" (revision: 09facfd) jenkins-OpenIDM - 5.5.x - postcommit-236 origin/sustaining/5.5.x and it happens on the all browsers.

Comment by Matthias Grabiak [ 15/Aug/18 ]

Hi Jakub, I have a question. How did you set up IDM, did you first install & upgrade to 5.5.1.1 and then set up the full stack sample, or did you start with a full stack sample in 5.5.1.0 and then run the upgrade on that? I wonder if that would make a difference. I would be curious if a functioning 5.5.1.0 full stack sample would break if an upgrade to 5.5.1.1 is performed.

Comment by Jakub Janoska [X] (Inactive) [ 15/Aug/18 ]

Hi Matthias Grabiak. I am seeing the same behavior for the both cases. But please note, that is necessary to disable AM authentication module before update - https://backstage.forgerock.com/docs/idm/5.5/install-guide/#update-prep.

Comment by Jakub Janoska [X] (Inactive) [ 15/Aug/18 ]

But I found another issue, which is related to upgrade and AM authentication module - OPENIDM-11531.

Comment by Mark Offutt [X] (Inactive) [ 31/Aug/18 ]

Reverted commit 0ac8a6c8571a40c5f41e723c545644c93cd4ef16 from 5.5.1.1 to see if it resolves the issue.

Comment by Jakub Janoska [X] (Inactive) [ 05/Sep/18 ]

yes, issue with "Session Expiration" is gone from 5.5.1.1 after revert - 0ac8a6c8571a40c5f41e723c545644c93cd4ef16.

Comment by Jakub Janoska [X] (Inactive) [ 03/Oct/18 ]

"Session expiration" issue is observed also for OpenIDM version "5.0.1.1-M1" (revision: 4b4af3a) jenkins-OpenIDM - 5.0.x - Release-39 sustaining/5.0.x (the same as "5.5.1.1-SNAPSHOT" (revision: 09facfd)).

Steps for reproduction is in comment above - https://bugster.forgerock.org/jira/browse/OPENIDM-10969?focusedCommentId=133344&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-133344.

Mark Offutt [X] Do we revert it also for OpenIDM 5.0.1.1?

Comment by Mark Offutt [X] (Inactive) [ 05/Oct/18 ]

Reverted from 5011. Retargetting for 5012.

Comment by Jakub Janoska [X] (Inactive) [ 10/Oct/18 ]

https://ci.forgerock.org/user/jakub.janoska/my-views/view/myList/job/OpenIDM%20-%205.0.x%20-%20Release/43/artifact/target/checkout/openidm-zip/target/IDM-5.0.1.1-RC2.zip still contains commit with fix (the same for OPENIDM-10968). Mark Offutt [X]

Comment by Jakub Janoska [X] (Inactive) [ 16/Oct/18 ]

Correctly reverted from OpenIDM version "5.0.1.1-RC5" (revision: 14db46f) jenkins-OpenIDM - 5.0.x - Release-46 sustaining/5.0.x

Generated at Thu Sep 24 13:57:55 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.