Changing the login and logout pages

<a class=wpsToolBarLink href='<%= wpsBaseURL %>/myportal'><wps:text key="link.login" 
    bundle="nls.engine"/></a>

The following example shows what the banner_toolbar.jspf will look like after adding the above anchor tag:

<%-- comment this to enable screen login --%> 
	<portal-logic:if loggedIn="no">
	<portal-navigation:urlGeneration contentNode="wps.Login">
<!--commented out the next href for Changing the Login Page
		<a tabIndex="7" class="toolbarLink" href='<% wpsURL.write(escapeXmlWriter); 
     %>'><portal-fmt:text key="link.login" bundle="nls.engine"/>
		</a>
	 -->
		<a tabIndex="7" class="toolbarLink" href='<%= wpsBaseURL %>/myportal'>
		 <portal-fmt:text key="link.login" bundle="nls.engine"/>
		 </a>
	</portal-navigation:urlGeneration>
	</portal-logic:if>
	
	<%-- Uncomment this to enable screen login  
	<portal-logic:if loggedIn="no" notScreen="Login">
		<a class="toolbarLink" href='<%= wpsBaseURL %>/myportal'><portal-fmt:text 
			key="link.login" bundle="nls.engine" /></a>
	</portal-logic:if>
	--%>

The following example shows what the mainMenu.jsp will look like after adding the above anchor tag:

<%-- Login button --%>
	<%-- Comment out to enable screen login --%>
	<portal-logic:if loggedIn="no">
		<portal-navigation:urlGeneration contentNode="wps.Login" themeTemplate="">
			<c:set var="menuTitle"><portal-fmt:text key="link.login" 
       bundle="nls.engine" /></c:set>
			<% if ( menuItemCount > 0 ) { %>,<% } %>
      "asynchDoFormSubmit('<%= wpsBaseURL %>/myportal');",
			'<c-rt:out value="<{menuTitle}" escapeXml="true" />',"
       <{defaultPageIconUrl}"
			<% menuItemCount++; %>
		</portal-navigation:urlGeneration>
	</portal-logic:if>
	<%-- Uncomment to allow screen login 
	<portal-logic:if loggedIn="no">
			<c:set var="menuTitle"><portal-fmt:text key="link.login" 
       bundle="nls.engine" /></c:set>
			<% if ( menuItemCount > 0 ) { %>,<% } %>
      "asynchDoFormSubmit('<%= wpsBaseURL %>/myportal');",
			'<c-rt:out value="<{menuTitle}" escapeXml="true" />',"
       <{defaultPageIconUrl}"
			<% menuItemCount++; %>
	</portal-logic:if>
	--%>

	pdadmin>user create user_name user_dn cn sn pwd

And then enter:

	pdadmin> user modify user_name account-valid yes

When a WebSphere Portal Express session is ended by clicking the Logoff button on the navigation screen, the ESM session is not invalidated. Subsequent requests to protected pages may still be allowed without providing a user name or password until both the ESM and the WebSphere Portal Express's login sessions are properly terminated. Learn how to invalidate the single sign on session of the ESM by reviewing the documentation provided by the ESM relating to logoff pages. Here is an example for each supported ESM:

• Tivoli Access Manager's WebSEAL by default provides http://webseal/pkmslogout as a special URL to terminate the WebSEAL single sign on session

In addition to configuring the ESM to provide this logoff capability, you should also enable WebSphere Portal Express to execute the ESM logoff URL after completing its logoff command. Enable WebSphere Portal Express to do this with the following configuration steps:

1. In configuration service, you can specify the following values:
   • redirect.logout= true
   • redirect.logout.ssl=false or true, depending on your environment
   • redirect.logout.url=protocol://host_name/logout_page
     where

     • protocol is the protocol of the ESM machine: http or https.
     • host_name is the fully qualified host name of the ESM machine.
     • logout_page is the ESM page that users will be directed to when they log out. Refer to the ESM Administrator's Guide for more information about using logout forms.
2. Perform the following steps to run the update-properties configuration task:
   1. Locate the directory /PortalServer/config
   2. Type the following configuration task appropriate for your operating system on a command line:
      • Windows: WPSconfig.bat update-properties
      • Linux: WPSconfig.sh update-properties