000037927 - Missing tabs and skewed buttons in the RSA Identity Governance & Lifecycle user interface after Google Chrome updates

Document created by RSA Customer Support Employee on Sep 10, 2019Last modified by RSA Customer Support Employee on Nov 4, 2019
Version 27Show Document
  • View in full screen mode

Article Content

Article Number000037927
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition:  7.1.x
Platform (Other): Google Chrome
 
IssueAfter updating Google Chrome to 76 or 77 many areas of the RSA Identity Governance & Lifecycle user interface are missing tabs. Symptoms include:
  • Missing tabs when editing a connector, collector, form or review definition.
  • Missing tabs when viewing review result items.
  • Missing tabs when performing a change request approval.
  • Inability to create an AFX connector due to missing tabs preventing the input of required information

In the following example, the tabs and part of the banner are missing when editing an AFX connector:


View in Chrome:

User-added image



View in Firefox, Internet Explorer, and prior versions of Chrome:

User-added image
 


After updating Google Chrome to V78.0.3904.70 released October 22, 2019, the above issues were resolved but a new issue has been introduced where buttons on certain screens are skewed. For example:
 


 User-added image
CauseThe first issue (missing tabs) is caused by a defect in Google Chrome V76 and V77.
The second issue (skewed buttons) is caused by a defect in Google Chrome V78.0.3904.70.
 
Resolution

RESOLUTION:


Both problems are fixed in Google Chrome version V78.0.3904.87. The resolution is to upgrade to that version by following the below steps:

  1. In the Google Chrome browser go to Help > About Google Chrome. This will start the upgrade process.
  2. Relaunch the browser.
 

NOTE:


If you implemented the style sheet workaround, you may remove the style sheet by following the below steps:

  1. In the RSA Identity Governance & Lifecycle user interface go to Admin > User Interface > Files tab > Choose Style Sheets from the drop down menu. 
  2. Click on the uploaded style sheet and press Delete.

User-added image


 


The change takes effect immediately.

 
WorkaroundThere are workarounds available (see below), but it is recommended that you upgrade your Google Chrome browser rather than implement these workarounds since the latest version of Google Chrome now resolves both issues.

WORKAROUND 1:


Use either Firefox or Microsoft Internet Explorer/Edge browsers. This resolves both issues.

WORKAROUND 2:



The second workaround uses a style sheet. The steps to implement differ between 7.1.x and 7.0.2 and are outlined below. This only resolves the first issue. Once on version 78, this will not resolve the second issue.




7.1.x


Download the attached blog1.css style sheet. This is meant to be a temporary workaround until a fix from Google is available. Once the fix is available, please remove this workaround.

NOTE: A previously published workaround was to use dialog.css. If you have already used dialog.css, please remove before using blog1.css.

IMPORTANT: If you already use a style sheet in RSA Identity Governance & Lifecycle, do not load blog1.css directly. Instead, append the code in blog1.css to your style sheet and reload your style sheet. If you have already appended the code in dialog.css, please remove that code before appending the code in blog1.css.



  1. Download the attached blog1.css style sheet.
  2. If you have your own style sheet, edit your style sheet and append the code in blog1.css to your style sheet. The contents of blog1.css are shown below:


@media screen and (-webkit-min-device-pixel-ratio:0){
#DialogIframe{
      max-height: -webkit-fill-available !important;
    }
}


  1. In the RSA Identity Governance & Lifecycle user interface, go to Admin > User Interface > Files tab > Choose Style Sheets from the drop down menu. 
  2. Upload blog1.css or your revised style sheet.
  3. The fix takes effect immediately.
  4. Once a fix from Google is available, please remove the style sheet or in the case of your own style sheet, remove the appended code.

7.0.2


Download the attached blog1.css style sheet. This is meant to be a temporary workaround until a fix from Google is available. Once the fix is available, please remove this workaround.

NOTE: A previously published workaround was to use dialog.css. If you have already used dialog.css, please remove before using blog1.css.

  1. Download the attached blog1.css style sheet.
  2. Login to the RSA Identity Governance & Lifecycle application server as the oracle user.
  3. Go to the /home/oracle/wildfly/standalone/deployments/aveksa.war/RSA/css folder.


cd /home/oracle/wildfly/standalone/deployment/aveksa.war/RSA/css


  1. Edit (vi) Main.css.
  2. Add the contents of the attached blog1.css file to the end of Main.css. The contents of blog1.css are shown below:


@media screen and (-webkit-min-device-pixel-ratio:0){
#DialogIframe{
      max-height: -webkit-fill-available !important;
    }
}


  1. Clear the browser cache and open the URL again.

Attachments

Outcomes