ShowTable of Contents
The accounts framework provides a programmatic means of creating, accessing, and interacting with account data. Account information can be used to authenticate with various IBM application servers or used to securely store data used by other plugins. Accounts can contain both persistent and transient data.
Accounts may be created and access through the Accounts preference page. A predefined account is the Home Portal Account used to access composite applications within WebSphere Portal.
Account information is used to pass credentials to the corresponding application server. The embedded browser and Java .net classes are integrated with the accounts API. For example, opening the URL http://dpi-portvm.atlanta.ibm.com/wps/myportal
automatically authenticates the Home Portal Account. This is because the URL in the browser address matches the Server URL in the Home Portal Account. At a high level, the following occurs.
- Compare the URL in the embedded browser's address bar to the Server values in Accounts. The Server value will be parsed when comparing; it is not necessary to match the Account's Server value to the server is the URL.
- An authentication attempt is made to the Authentication URL. If no Authentication URL is supplied, an attempt is made to the Server listed in the Account.
- Any tokens provided during authentication will be re-used by the Accounts framework.
Sample code is being moved. This article will be updated when posting is complete.
The accounts plugin provides an extensible means of adding accounts to the Expeditor platform. Contributors can add extensions to declaratively define account information. The plugin consumes these extensions and creates the resulting Expeditor Account. Consult the plugin.xml to reference mock accounts. These accounts will be auto-created when the platform launches.
Running the Sample
To execute the sample, simply add the plugin to the Expeditor platform. The plugin creates accounts through the IStartup extension when Expeditor launches.