> Oracle WebCenter Interaction Administrator Guide > Configuring Advanced Properties in the Portal Configuration Files > Modifying the portalconfig.xml File > Authentication

Oracle WebCenter Interaction Administrator Guide

     Previous Next  Open TOC in new window   View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Authentication

The following configuration parameters apply to authentication.

Parameter Description
AllowGuestAccess Allow the guest user to access the portal. If guest access is not allowed, the portal will always prompt for login information.
GuestRedirectToLogin If the guest user does not specify a space in the URL query string, this setting determines the initial page the user sees.

Users can navigate to different portal pages by including space=xxxx strings in the URL query string. For example, if the user were to type: http://MYSERVER/portal/server.pt?space=MyPage, the user will be directed to the My Page (the access privileges of that page will be in effect).

However, if the user did not include a space=xxxx string in the query string (that is, the user only typed: http://MYSERVER/portal/server.pt), the portal directs them to a default page, depending on the GuestRedirectToLogin setting and the experience definition settings, as follows:
  • 0: The portal will redirect the guest user to the home page defined in the current experience definition (usually a My Page or community page).
  • 1: The portal will redirect the guest user to the login page as defined in the current experience definition.
RedirectOnLogout After logging out the user is redirected to a default page as follows:
  • 0: The portal will redirect the guest user to the home page defined in the current experience definition (usually a My Page or community page).
  • 1: The portal will redirect the guest user to the login page as defined in the current experience definition.
AuthTokenExpiration This setting allows you to set how long the portal remembers your login password after doing an HTTP Basic Authentication for WebDav. The value should be formatted in minutes and is defaulted to 30 minutes. Entering 0 will disable the cookie from being set.
AllowDefaultLoginPageAuthSource Controls the use of the default authentication source for portals (that do not use single sign-on) on the login page and Login Portlet. It also lets you configure the authentication source drop-down list.
DefaultAuthSourcePrefix Sets the default authentication source prefix that will be prepended to the login name when users log into your system, unless they select another authentication source from the drop-down list on the login page. In the case of SSO, this is the authentication source category for all of your SSO users.
You can use AuthSourcePrefix tags to order the items in the authentication source drop-down list. Entries in the list should look like the following:
<AuthSourcePrefix[i] value="Auth Source Prefix">
</AuthSourcePrefix[i]>

Where [i] is replaced with the items' order in the drop-down list (starting with 1).

To include the WCI Authentication Source in the list, simply make an entry with “WCI Authentication Source” as the value. The WCI Authentication Source is for users who are created in the portal, manually, through invitations, or through the Create an Account page. For example, to include the WCI Authentication Source as the third item in the drop-down list, use the following tag:
<AuthSourcePrefix3 value=“WCI Authentication Source”> 
</AuthSourcePrefix3>

Authentication source prefixes in the ordered list are displayed first in the drop-down list and are followed by any authentication sources not included in the ordered list.
Authentication Source Mode Purpose Appearance Required Actions
0 The portal does not use the default authentication source. The drop-down list has no special ordering. Default mode.
1 The portal uses the default authentication source. The drop-down list is hidden, but it displays a link that brings up the authentication source drop-down list. This lets users select a non-standard authentication source. You must turn off the caching on the Login Portlet or disable the Login Portlet.

You must set the DefaultAuthSourcePrefix tag to the prefix of the authentication source that is the default for all users.

2 The portal uses the default authentication source. The drop-down list is not hidden, and the default authentication source is pre-selected. You must turn off the caching on the Login Portlet or disable the Login Portlet.

You must set the DefaultAuthSourcePrefix tag to have the prefix of the authentication source that is the default for all users.

3 The portal uses the default authentication source. The drop-down list is permanently turned off.  
AllowAutoConnect Setting for saving passwords in cookies.
  • 0: Turns off the option of saving passwords in a cookie.
  • 1: Users will see a “Remember my password” check box on the login page of your portal. Passwords are saved as cookies for users that select this check box, which lets users who navigate to your portal be logged in automatically.
SSOVendor Sets the single sign-on configuration. For information on SSO, see Deploying Single Sign-On.
CaptureBasicAuthenticationForPortlets Determines whether or not to capture basic authentication information (login and password) and store it in the session (to send to portlets). The basic authentication information cannot be captured when users select “Remember my password” to login via a cookie.
  • 0: The authentication information will not be stored in the session.
  • 1: The authentication information will be stored in the session.
RememberPassword This setting allows you to set how long the portal remembers your login password. The value should be formatted in minutes. The default is one week.
BrowserLoginTokenExpiration This setting allows you to set whether or not the portal caches a login token in a browser session cookie that will expire when the browser is closed. Entering 0 will disable the cookie from being set, and is the default value. Entering a positive number controls how long the login token will remain valid. Note that the cookie is only valid as long as the browser is open, so if the user closes their browser, the login token will be removed. The login token expiration is an upper limit if they don't close their browser. A reasonable value for this would be 600 minutes (one workday). The value should be formatted in minutes.
Note: The BrowserLoginTokenExpiration setting is only active when AllowAutoConnect is set to 1.
Parent topic: Modifying the portalconfig.xml File

  Back to Top      Previous Next