Setting up a portal on your own domain

Note: Before you begin this task, you must already have a valid host name in DNS that is mapped to the Infor-provided host name, using an alias, and you must have a signed digital certificate for your host name. This setup is typically performed by a network administrator or other IT professional and is not part of the IPF portal setup. In general, these tasks must be completed:
  1. Assuming your original domain/subdomain is already registered, add the new host name to use for your portal website and obtain a signed digital certificate for it. See "System requirements" for certificate requirements.

    We recommend that this task is performed first, because an organization must prove that they own a domain in order to obtain a signed certificate. If the portal host name on your domain is aliased to the Infor-provided host name first, the request for a certificate may be denied.

To add your new host name in IPF, follow these steps:

  1. Open a supported Web browser and enter the URL for the Portal Manager in the PRD portal environment, which was provided by the Infor Cloud team.
  2. Sign in to the Portal Manager using the same portal administrator credentials that are used for the TRN environment.
  3. Select Environment Configuration > Digital Certificates.
  4. On the toolbar, click Import.
  5. Select the digital certificate .p12 file that was obtained for the portal host name on your domain and click Open.
  6. Specify the password for this .p12 file and click OK.
  7. Select Environment Configuration > Host Names.
  8. In the Host Names list, select the Infor-provided host name and then on the toolbar, click New.
  9. Specify the host name for the portal on your domain, which was mapped to the Infor-provided host name, and click OK.
  10. On the toolbar, click Edit.
  11. Specify this information:
    Digital Certificate for HTTPS
    Select the digital certificate that was imported for the portal host name on your domain (in step 4).
    User Login Timeout Settings
    Specify the login timeout settings for the portal. These are your options:
    • Expire when browser is closed: The user login is expired when the browser is closed. The user must log in again to use the portal.
    • Expire after timeout interval in minutes: The user login is expired after the specified number of minutes. If you specify a timeout interval, you can also select to reset the expiration timeout when the user performs any actions in the browser within the timeout interval. If you do not select to reset the expiration timeout, then the user login is expired after the timeout interval, regardless of their browser activity.
    • Expire all user logins created before: This option allows you to select a date for expiring all existing user logins.
    • Update: At any time, you can click the update icon, which causes all logins to expire immediately.
  12. Click Save.
    Note: If you have multiple mapped subdomains, you must create a host name record for each and edit each record to assign the wildcard digital certificate.