Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Supplier 360
  3. Supplier 360 Installation Overview
  4. Before You Install
  5. Installing the Supplier 360 Components
  6. After You Install
  7. Business Processes for Supplier Management
  8. Customizing Supplier 360
  9. Upgrading MDM - Supplier 360
  10. Troubleshooting

Prerequisites to Access SSL-enabled Product 360 Supplier Portal on Google Chrome

Prerequisites to Access SSL-enabled Product 360 Supplier Portal on Google Chrome

You can access the SSL-enabled Product 360 Supplier Portal using any of the supported browsers. If you use the Google Chrome browser, you can't access the SSL-enabled Product 360 Supplier Portal through the HTTPS protocol because the browser blocks the same-site cookies.
To access the SSL-enabled Product 360 Supplier Portal, enable the Supplier 360 Portal to use the HTTPS mode and embed the Product 360 Supplier Portal within an iFrame.
  1. Enable the Supplier 360 Portal to use the HTTPS mode.
    For more information about enabling HTTPS mode for the Supplier 360 Portal, see the Enable Secure HTTPS communication Knowledge article.
  2. Go to the following directory:
    <Product 360 Supplier Portal installation directory>/configuration
  3. In the configuration.properties file, set the value of the
    cookie.secure
    attribute to
    true
    .
  4. Go to the following directory:
    <Product 360 Supplier Portal installation directory>/tomcat/conf/
  5. In the server.xml file, enable the Product 360 Supplier Portal to use the HTTPS mode.
    For more information about enabling HTTPS mode for the Product 360 Supplier Portal, see the
    Informatica MDM - Product 360 10.5 – Installation Guide
    .
  6. In the web.xml file, set the value of the
    session-config
    and
    cookie-config
    attributes to
    true
    .
  7. In the context.xml file, add the
    <CookieProcessor sameSiteCookies="None" />
    element to the
    <context>
    block.
    The following example shows the context.xml file with the addition of
    <CookieProcessor sameSiteCookies="None" />
    element:
    <Context antiResourceLocking="true"> <WatchedResource>WEB-INF/web.xml</WatchedResource> <WatchedResource>${catalina.base}/conf/web.xml</WatchedResource> <Manager pathname="" /> <CookieProcessor sameSiteCookies="None" /> </Context>

0 COMMENTS

We’d like to hear from you!