Accounts frameworkAdded by IBM on October 5, 2011 | Version 1 (Original)
|The Accounts framework enables you to store, access, and use properties that are required to make a connection to, and communicate with, a local or remote service.
The Accounts framework enables you to store, access, and use properties that are required to make a connection to, and communicate with, a local or remote service.
Some examples of accounts include:
- An HTTP account that is used to connect to a web-based service. This account contains a URL for the location of the service, and a user name and password to log onto the service.
- An Instant Messaging account, used by an instant messaging client to connect to an IM server, such as IBM® Lotus® Sametime®. This account includes a server name, and a user name and password to connect to the instant messaging server. The account could also be used to store user preferences such as the text people see when the user's status is “Away.”
An account can store both connection properties, and properties or preferences specific to that connection. The Accounts API provides a way to get, add, update, remove, and listen for changes to an account. The component ensures that once user accounts have been created, either manually by a user or automatically during provisioning, users will only ever have to enter one password to access all of the services for which they have accounts. The Accounts component also provides a common user interface from which users can see and change account information and passwords for all of their services.
Adding accountsParent topic: Securing applications and data
The Account class represents an account and all of its data.
You can retrieve an existing account using methods provided by the AccountsManager
You can update existing accounts using methods provided by the AccountsManager
Listening for account changes
You can add an implementation of the AccountChangeListener
to listen for changes to existing accounts or for accounts being created.
Implementing a custom account type
You can extend the Account class using the Accounts extension point. Every account has an account type. Each account of a given type can either use the base Account class provided by the API or create and register a class that extends the Account class and provides additional functionality.
Authentication and accounts
If the HTTPS (or HTTP) site needs to be authenticated, you create an account first, either programmatically or by using the account tool.
Configuring the platform to not save user passwords in accounts
For security reasons, you may not want to allow users to save their passwords in Accounts. You may instead desire for the user to enter his or her password each time they log into a server.
Sharing account credentials
Multiple accounts can be configured to share the same credentials.