Configuring Web Profiles

Select to enable users to view the report repository. When this check box is deselected, no report files can be viewed by users.

This check box is selected by default.

(Optional) Specify a drive and directory path to indicate where the site that is served by this web profile should look for generated reports.

This value overrides the location that is specified during the PeopleSoft Pure Internet Architecture setup; you can leave this field blank to use the original value.

Specify how reports should be compressed:

All Browsers: Reports are always compressed. This is the default value.

Exclude Netscape: Reports are compressed, except for users who are using Netscape Navigator.

Do Not Compress: Reports are never compressed.

Select to enforce SSL if the entire website requires the SSL protocol. This prevents users from using non-SSL protocols to access any link within this website or application.

If only some pages require SSL access, deselect this check box (the default setting).

Select to prevent the single sign on token from traveling over an insecure network. If you select this check box and the scheme of the current request is HTTPS (an SSL server), the system sets the secure attribute of the single sign on cookie (PS_TOKEN) to True.

PeopleSoft single sign on functionality also applies at the web server level. For example, suppose that you have two web servers: server X and server Y. Web server X is an SSL site, and web server Y is not. In these situations, many sites want server Y to trust the authentication token, PS_TOKEN, issued by server X. This requires that you set the PS_TOKEN to be secure.

If the PS_TOKEN is not secure, when a user signs in through server Y, the browser sends PS_TOKEN to server Y over the unencrypted, non-SSL link. This is typical behavior for browsers when dealing with cookies that aren't secure. Potentially, in this situation, a hacker could obtain this token from the clear network and use it to sign in to the SSL-secure server X.

Another important use of this property relates specifically to the PeopleSoft portal. When the portal uses a proxy server to relay content with an HTML template, it should forward only PS_TOKEN cookies that are marked secure over SSL connections.

If, at your site, you want users to sign in to an HTTPS server, and then want to use single signon functionality with HTTP servers, deselect this check box to enable single signon functionality between HTTPS and HTTP servers.

This check box is selected by default.

Specify the number of seconds that the portal should wait before warning users that the browser session will expire. Users can continue with the current session by clicking the OK button in the warning message, which resets the inactivity timer. If a user doesn't respond within the inactivity logout interval, the session ends and the expired connection page appears.

The default value is 1080 seconds (18 minutes).

Specify the number of seconds of inactivity after which the HTTP session times out for authenticated users. When the interval passes with no user activity, the web server discards all session information, including cached page states. The next time the user submits a request, the web server creates a new HTTP session. From the user experience, the user may be put in a search page or home page because the previous session state is lost at this point. This property is unaffected by any permission list setting.

When this property isn't specified, the HTTP session time-out interval is the same value as the authenticated user inactivity logout property that is specified on this page.

This property is similar to the public users HTTP Session Inactivity property that is specified on this page.

Use this property with caution. Don't use this property if you don't understand its usage.

Specify the value in seconds of the inactivity time-out interval that applies to PeopleSoft applications to which a user is signed in. When the interval passes with no user activity, the user's browser displays the page that is specified by the Expire Page - Page field on the Web Profile Configuration - Look and Feel page. The web server applies this value in JavaScript.

The default value is 1200 seconds.

Displays the name of the time-out warning script that is currently in effect. The default value is WEBLIB_TIMEOUT.PT_TIMEOUTWARNING.FieldFormula.IScript_TIMEOUTWARNING.

Click to change the time-out warning script. The Override Timeout Warning Script page appears, with these fields:

• Record (Table) Name: The default value is WEBLIB_TIMEOUT.

• Field Name: The default value is PT_TIMEOUTWARNING.

• PeopleCode Event Name: The default value is FieldFormula.

• PeopleCode Function Name: The default value is IScript_TIMEOUTWARNING.

The values of these fields are concatenated to produce the value in the Timeout Warning Script field.

Select so that the system bypasses the user sign-in page when users click a direct link to a page. The system uses the values that you specify in the User ID and Password fields for authentication. This check box is deselected by default.

When you select this check box, the system enables the User ID, Password, and HTTP Session Inactivity fields.

Enter the account that the system uses to authenticate public users. This field is enabled when you select the Allow Public Access check box.

Enter the password for the account that you entered in the User ID field. This field is enabled when you select the Allow Public Access check box

Specify the value in seconds of the inactivity period that applies to public users.

When the period passes with no user activity, the web server discards all session information, including cached page states. The next time the user submits a request, the web server creates a new HTTP session.

This field is enabled when you select the Allow Public Access check box.

The default value is 1200 seconds.

See SwitchUser.

Specify the amount of time to wait while disconnecting the Oracle Jolt connection. A value of 0 means no limit.

The default value is 0 seconds.

Specify the maximum number of seconds that the servlet allows for a request to be sent to the application server. This setting does not indicate a maximum amount of time for the service to finish; it indicates only the maximum amount of time to send the request to the application server.

The default value is 50 seconds.

Specify the maximum number of seconds that the servlet should wait for a response from the application server.

Make sure that the value of this field is greater than your application server service time-outs, such as the Service Timeout setting for PSAPPSRV that appears in the psappsrv.cfg configuration file on the application server.

The default value is 600 seconds.

Enter the user account that the system uses to authenticate users for XML Link technology.

Enter the password for the account name that you entered in the User ID field.

Select to indicate that the portal should use the HTTP protocol instead of HTTPS for requests that are issued by the xmllink servlet for content that is hosted on the same server as the xmllink servlet.

This check box is selected by default.

Specify the default protocol—HTTP or HTTPS—to override the protocol that is used by the PeopleSoft Pure Internet Architecture and the portal to construct URL references. When this property is omitted, the protocol of the incoming request to the PeopleSoft Pure Internet Architecture servlet is used.

You must set this property when the browser makes an SSL connection and SSL is terminated before the PeopleSoft Pure Internet Architecture servlet, using a device such as an SSL accelerator or a reverse proxy server, or when you select the PIA use HTTP Same Server property on the Web Profile Configuration - Security page. In this situation, the protocol of the request to the PeopleSoft Pure Internet Architecture servlet is HTTP, but the PeopleSoft Pure Internet Architecture must generate URL references with an HTTPS protocol.

Enter a default server name to override the server name that is used by the PeopleSoft Pure Internet Architecture and the portal to construct URL references. When this property is omitted, the server name of the incoming request to the PeopleSoft Pure Internet Architecture servlet is used to construct URL references.

You must set this property when the server on which the PeopleSoft Pure Internet Architecture servlet resides is different from the server to which the browser is connected. This can occur when a reverse proxy server or load balancer is configured in front of the web server. In these situations, the PeopleSoft Pure Internet Architecture must generate URL references with the server that is used by the browser for its initial connection.

Enter a default port to override the port that is used by the PeopleSoft Pure Internet Architecture and the portal to construct URL references. When this property is omitted, the port of the incoming request to the PeopleSoft Pure Internet Architecture servlet is used to construct links on a PeopleSoft Pure Internet Architecture or portal page.

You must set this property when the port through which the PeopleSoft Pure Internet Architecture servlet is accessed is different from the port to which the browser is connected. This can occur when an SSL accelerator is used or when a reverse proxy server is configured in front of the web server, and the reverse proxy server or load balancer listens on a different port from the web server, or when you select the PeopleSoft Pure Internet Architecture use HTTP Same Server property on the Web Profile Configuration - Security page. In these situations, the PeopleSoft Pure Internet Architecture must generate URL references with the port that is used by the browser for its initial connection.

Specify the name pattern for cookies to which this rule applies. For example, to specify all cookies whose names start with HR_, enter the value HR_*.

Specify the name pattern for the servers to which the specified cookies should be passed. For example, to specify all servers in the domain .hr.example.com, enter the value *.hr.example.com. You can use a substitution parameter %AuthTokenDomain to represent the authentication domain currently in effect.

Specify the name pattern for the servers to which the specified cookies should not be passed. You can use a substitution parameter %AuthTokenDomain to represent the authentication domain currently in effect.

Select to indicate that the cookie should be deleted when the user signs out of the portal.

Cookies are sent secure by default over secure (HTTPS) connections. Select this setting to disable the secure attribute for this cookie, which allows it to be sent in requests over insecure (HTTP) connections. This setting applies only when HTTPS is being used.

Specify the name pattern for cookies to which this rule applies. For example, to specify all cookies whose names start with HR_, enter the value HR_*.

Select to indicate that the cookie can be accessed by JavaScript from the browser side.

Cookies are sent secure by default over secure (HTTPS) connections. Select this setting to disable the secure attribute for this cookie, which allows it to be sent in requests over insecure (HTTP) connections. This setting applies only when HTTPS is being used.

Select a protocol (http or https) to restrict requests from this host to that specific protocol.

Enter a fully qualified host name (for example, host.example.com), a domain name (for example, .example.com), or a subdomain name (for example, .us.example.com).

Specify a port number to restrict requests from this host to that specific port number.

Select this check box to add this entry to the allowlist for CORS processing.

Select this check box to add this entry to the allowlist to allow the site to embed content from this web server.

Select this check box to add this entry to the allowlist for participating in single signon.

Select this check box to turn on control of which sites can embed content from this web server.

Select this check box to authorize all hosts within the same authentication token domain as this web server.

Select this check box to authorize any hosts in the Authorized Sites Grid with the Framable check box also selected to embed content from this web server.

Select to indicate that PeopleSoft application pages should be cached by the user's browser. For security reasons, deselect this check box in kiosk environments.

This check box is selected by default.

Specify how many browser states the portal should support when the user accesses PeopleSoft application pages.

The default value is 5 states.

When a user signs out (either explicitly or because of a session timeout), the system normally clears all application states for the user's session. This property enables clearing of application states for individual windows instead. If your users have a long session time-out and many browser windows open, use this property to force the portal web server to release cached states for windows that a user has closed.

Every time a user clicks the New Window link on a portal page, or when transfer PeopleCode opens a new window, the portal web server creates and maintains a state cache for that new browser window. Even if the user closes the window, the web server continues to maintain the cache during the interval that is specified by the Inactivity Logout field on the Web Profile Configuration - Security page. If users open many application browser windows simultaneously and then close most of them while still continuing to work actively in one or two remaining windows, you may be using more web server memory than is required and unnecessarily degrading its performance.

You can improve performance by using this property to specify an independent time-out interval that applies to individual browser windows, which forces the portal web server to release cached states for windows that users have closed.

When a user clicks the New Window link, and each time user activity in a window produces a request for data from the web server, the portal applies a current timestamp to its corresponding state cache. The next time the user clicks the New Window link, the portal examines the timestamp for each state cache. For any timestamp that's older than the status block time-out, the portal web server discards the associated window state cache on the assumption that the window must have been closed.

Enter a value that represents the number of seconds for the inactivity time-out per window. This time-out should be as short as possible, but still long enough to avoid discarding the state cache of any window that's still in use. A good starting value is the same value as the inactivity logout. If you don't specify this property, or if you enter 0,status blocks are tracked per session—all status blocks are deleted when the user signs out or when the inactivity logout interval expires.

Select to apply homepage caching on the browser. When this check box is selected, the Homepage Stale Interval field and the Browsers grid become available.

This check box is selected by default.

When the Cache Homepage check box is selected, the following occurs:

• All non-component-based pagelets will be cached on the browser by default unless the pagelet has a PORTAL_NOBROWSERCACHE content reference attribute set to Y.

• Component-based pagelets will not be cached on the browser by default unless the pagelet has a PORTAL_NOBROWSERCACHE content reference attribute set to N.

  Important! Do not enable homepage caching for any component-based pagelet that uses interactive processing mode.

When this check box is deselected, any PORTAL_NOBROWSERCACHE content reference attributes are ignored.

Enter the number of seconds that the browser should wait before requesting an updated homepage from the portal server.

The default value is 1200 seconds (20 minutes).

Select to enable caching of proxied JavaScript objects on the portal server. This check box is selected by default.

Select to enable metadata caching. This check box is selected by default.

Enter the number of seconds that should pass before the portal refreshes the metadata cache. The default value of this property is 86400 seconds (24 hours).

Select to cache all target content HTML that has an appropriately defined Cache element. This check box is selected by default.

Select to enable web server-based navigation caching.

For all profiles, including those that are newly created, the default value is False.

Specify the maximum total number of HTTP requests that the web server should receive for metadata objects before it purges the metadata cache, forcing the portal to refresh the cache.

The default value is 1000 requests. Set this property to 0 to disable the feature.

Enter the image file cache directory.

The default value is /cache.

Enter the image file web cache directory.

The default value is /cache.

Enter the cascading style sheet (CSS) cache directory.

The default value is /cache.

Enter the CSS web cache directory.

The default value of this field is /cache.

Select to have the system write a copy of the image and CSS cache with no version number. This check box is provided in case an external reference to the PeopleSoft stylesheet is needed.

This check box is deselected by default.

Enter the directory of the cache for the chart image file.

The default value is /cache/chart.

Enter the directory of the web cache for the chart image file.

The default value is /cache/chart.

Enter the Java Script cache directory.

The default value is /cache.

Enter the JavaScript web cache directory.

The default value is /cache.

Select to temporarily store recent (persistent) search results on the browser and web server. Deselecting this setting suppresses all search persistence property settings that you configure in Application Designer definitions. The default value is unchecked.

Select to temporarily store recent (persistent) search results on the web server. Deselecting this setting suppresses all search persistence property settings that you configure in Application Designer definitions. This option applies only when you use either Internet Explorer 7 or Safari 3 as your browser. The default value is unchecked.

Displays the script to which the system redirects users after a successful sign-in. This value references the iScripts that build the PeopleSoft navigation.

The default value is WEBLIB_PTBR.ISCRIPT1.FieldFormula.IScript_StartPage.

Click to change the start page script. The Override Start Page Script page is displayed with these fields:

• Record (Table) Name: The default value is WEBLIB_PTBR.

• Field Name: The default value is ISCRIPT1.

• PeopleCode Event Name: The default value is FieldFormula.

• PeopleCode Function Name: The default value is IScript_StartPage.

The values of these four fields are concatenated to produce the value of the Page field on the Look and Feel page.

Displays the name of the component used to render fluid homepage tabs. The default value is NUI_FRAMEWORK.PT_LANDINGPAGE.GBL.

See Web Profile Configuration - General Page for more information.

Displays the HTML page containing text variables that are defined in text.properties. This page appears when user inactivity exceeds the limit that is specified by the Inactivity Logout field in the Authenticated Users region of the Web Profile Configuration - Security page.

Do not change this setting.

The default value is expire.html,expire.wml.

Enter the content name that is stored in the HTML catalog. It appears when a page has expired due to reaching the limit that is specified by the Number of States Supported field in the On the Browser region of the Web Profile Configuration - Caching page.

Change this value with caution.

The default value is PT_EXPIRE,PT_EXPIRE_WML.

Enter the name of the page that is used in Java to handle exceptions.

Change this value with caution.

The default value is exception.html,exception.wml.

Enter the name of the multichannel framework authorization failure page.

The default value is mcferror.html.

Enter the name of an initial error message page to be displayed in the user's browser when a portal pagelet is unavailable.

The default value is portalerrorpagelet.html.

Enter the name of an initial error message page to be displayed in the user's browser when target content is unavailable.

The default value is portalerrortarget.html.

Enter the name of an error message page that can be displayed in the user's browser to provide more detail about an error when retrieving portal content.

The default value is portalerrordetail.html.

Enter the name of the page to be displayed when the site being accessed is configured with an authentication domain (or web server session cookie domain), and the URL from the browser doesn't include the domain. This page contains a link to a sign-in page that produces the correct URL for the site. You can modify the content interface and design, but do not change the internal meta-tags that generate the correct URL.

The default value is authtokenenabled.html.

Enter the name of the page to be used to set trace parameters. If you enable tracing, this page appears before the sign-in page so that you can set the trace parameters and then sign in to the system.

The default value is signintrace.html.

Enter the name of a page to be displayed when the browser does not accept cookies. You should configure browsers to accept cookies.

The default value is cookiesrequired.html.

Displays the name of the page that should appear if the Secured Access Only check box is selected in the SSL region of the Web Profile Configuration - Security page, and the user is unable to proceed without SSL.

Do not change this setting.

The default value is sslrequired.html.

Displays the name of the page that appears when the user clicks the link from a password-expired page.

Do not change this setting.

The default value is userprofile.html.

Displays the name of the page that redirects to the servlet for the sign-in process.

Do not change this setting.

The default value is signon.html,signon.wml.

If your portal site is configured with sign-in PeopleCode to additionally validate the user, that code can call a result document if the user authentication failed. You can present the result document to the user in several ways by specifying one of these HTML documents in this field:

signonresultdoctext.html: The result text is wrapped in a standard portal error page. This is the default value.

signonresultdocpage.html: The result text itself is formatted as the error page.

signonresultdocredirect.html: This page redirects the user to your own result document, using the <%=resultDoc%> session variable element.

Enter the name of the page that should appear when the user makes an error signing in. To customize your sign-in page, clone signin.html as a starting point.

Change this value with caution.

The default value is signin.html,signin.wml.

Enter the name of the page that should appear when the user signs out. You may define a custom logout page.

Change this value with caution.

The default value is signin.html,signin.wml.

Displays the name of the page that should appear when the user password is expired.

Do not change this setting.

The default value is passwordexpired.html.

Displays the name of the page that should appear when the user's password is about to expire in the number of days specified in PeopleSoft security.

Do not change this setting.

The default value is passwordwarning.html.

Displays the Change Password page content ID. The system uses the value in passwordexpired.html to take the user to the Change Password page when a password is expired.

The default value is MAINTAIN_SECURITY.EXPIRE_CHANGE_PSWD.GBL.

Click to override the expired password change page. The Override Change Password on Expire Page page appears.

• Menu Name: The field is blank by default.

• Component: The field is blank by default.

• Market: The default value is Global.

Displays the content ID for the Change Password page. The system uses the value that you enter in passwordwarning.html to take the user to the Change Password page when a password warning is required.

The default value is MAINTAIN_SECURITY.CHANGE_PASSWORD.GBL.

Click to override the Password Change Warning page. The Override Change Password on Warning Page page appears.

• Menu Name: The field is blank by default.

• Component: The field is blank by default.

• Market: The default value is Global.

Send the cookie in first-party contexts only; the cookie is not sent in requests initiated by third-party websites.

Do not send the cookie on normal cross-site sub-requests (for example to load images or frames into a third party site); however, do send the cookie when a user is navigating to the originating third-party site (for example, when following a link).

Send the cookie in all contexts: in response to both first-party and third-party requests. The Secure attribute must also be set when the SameSite attribute is set to None; otherwise, the browser will reject the cookie. See Configuring Cookie Rules for more information.