Portal Server Mobile Access software supports the authentication modules provided by Sun Java System Portal Server software. This chapter describes three authentication modules that can be useful to portal sites offering mobile access:
If your site specifications require it, you can allow users to log in to the mobile PortalDesktop without being prompted for a userID.
Log in to the Sun Java System Access Manager administration console as the administrator. By default, Access Control tab is selected and the Realms page is displayed. You can see the available Realm Names in the Realms table.
Click the india realm. The india?Properties page is displayed under which the Realm Attributes of india realm are listed.
Click the Authentication tab. The india?Authentication properties are displayed. Check whether the NoPasswordModule Instance is available under the Module Instances table.
Click the ldapService Authentication Chaining in the Authentication Chaining table. The ldapService?Properties page is displayed. The available Instances are displayed.
If you does not have the ldapService as the Default Authentication Chain or the Administrator Authentication Chain, then you would not be enforced for NoPassword Authentication. If NoPassword authentication is required, then add the NoPassword to the respective configured Authentication Chain. For Default Authentication Chain, add the NoPassword to the respective configured Authentication Chain. In the default installation scenario both will be configured for ldapService.
Choose the NoPassword instance.
Click the Add button. The NoPassword instance is added to the Instance list.
Click the Save button. You will get the information that the authentication chain properties were updated.
Click the Logout button.
Try to login again to the Sun Java System Access Manager administration console. You will get a message that This server uses NoPassword Authentication.
If you want a user to access your portal site to explore what the experience of an authenticated user is, you can allow users to log in to the mobile Portal Desktop as anonymous users. This feature presents a snapshot of the mobile and voice Portal Desktop of a user with an authenticated session.
Anonymous users cannot change, store, or alter the content or configuration of channels with stateful data. If you support anonymous authentication, make sure that these channels are not available to these users.
To implement anonymous authentication, see the Sun JavaTM System Portal Server 7.1 Administration Guide.
The Portal Desktop for anonymous authentication uses the WirelessDesktopDispatcher as well as device-specific containers for both JavaServer PagesTM (JSPTM) software and templates. All channels to be displayed to the anonymous user must be included in these containers, just as they are for authenticated users.
Create the appropriate device-specific container.
Alter the WirelessDesktopDispatcher in the anonymous user?s display profile to use the new container for that particular device type.
The users of an organization can be configured to authenticate using MSISDN-Mobile Station ISDN, a standard international telephone number used to identify a given subscriber. This allows the users to log into the mobile portal desktop without the user passing authentication credentials. This feature limits the format of the login URL. The following format for the URL is recommended:
http://access-manager-host:port/service-deploy-URI/UI/Login?module-MSISDN&org-name
To implement MSISDN authentication and how to configure it, see the Sun Java System Access Manager 7 2005Q4 Administration Guide.