IBM BPM, V8.0.1, All platforms > Securing IBM BPM and applications > Configure administrative and application security
Configure administrative security
During installation, all components default to the primary administrative credentials that you provide. These default values provide basic security, but to enhance the security of your installation, configure the various components of IBM BPM with appropriate security identities.
When you create an IBM BPM profile and keep Enable administrative security selected, you are prompted for a user name. This identity is used as a default for all underlying components. Configure these identities after you create profiles to further enhance your security
When you configure IBM BPM, you augment the default profile. Part of this profile augmentation process involves providing a user name and password at various portions of the response file. The user names and passwords that you provide must correspond to an identity in the user registry chosen for this profile.
The user names and passwords you supply are required when you enable
administrative security.
Several components of IBM BPM use authentication aliases. These aliases are used to authenticate the runtime component for access to databases and messaging engines. You can modify these aliases on the Business Integration Security page of the administrative console.
Several components of IBM BPM use authentication aliases. These aliases are used to authenticate the runtime component for access to databases and messaging engines. The profile augmentation process collects a valid user name and password used to create these aliases.
- Start and stop the server
When administrative security is enabled, you must provide the appropriate user name and password to stop the server. The server will start without authentication, however, that authentication is required to access the administrative console. - Administrative security roles
Several administrative security roles are provided as part of the IBM BPM installation.