Security features of WebSphere Integration Developer
WebSphere Integration Developer features numerous improvements to WebSphere test environment security. For all test environment servers that were automatically created when the WebSphere test environment was installed, a number of security enhancements have been implemented. You can use the default security configuration to work with server security “out of the box” without making significant changes to the configuration in either WebSphere Integration Developer or the server administrative console.
A new Security preferences page enables you to modify the server administrative security settings in all of your current and future workspaces to match the server administrative security settings that have been specified in the server administrative console.
The following are the security features of WebSphere Integration Developer as:
Administrative security is enabled by default. It determines whether security is used at all, the type of registry against which authentication takes place, and other values, many of which act as defaults. The settings include the authentication of users, the use of Secure Sockets Layer (SSL), and the choice of user account repository. Additional information on administrative security is found in the WebSphere Process Server topic Administrative security.
Application security is enabled by default. It enables security for the applications in your environment. This type of security provides application isolation, role-based authorization, and requirements for authenticating application users. Application security is in effect only when administrative security is enabled.
Default user ID and password for server security
The default user ID and password for server security is now admin. The user ID and password have been added to the file-based repository, which is the registry used by default It is generally recommended that you change the default user ID and password to better secure your test environment servers and business integration applications. Although you can change the user ID and password for a server using the server administrative console, you must ensure that your changes to the user ID or password in the administrative console are also specified in the corresponding WebSphere Integration Developer server configuration.