Getting Started with WebSphere Application Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
154 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Community Edition<br />
If you chose BASIC as your Web project’s authentication method, a dialog window will be pop-up as<br />
shown in Figure 8.5<br />
Figure 8.5 – Popup dialog for ID and password<br />
The dialog will pop-up when you try to access a Web project’s context path the first time, and then the<br />
browser can record your login information so that the dialog doesn’t show again unless you reopen the<br />
address in a new browser.<br />
For example, if you type andy as the id and password, the Web project will deny you access because<br />
andy was defined earlier as a general user. Figure 8.6 shows the error message you would receive.<br />
Figure 8.6 – Access denial<br />
8.4 Managing users and groups for Community Edition administrative interface<br />
All Java EE application servers should have secure access to their administrative interfaces (such as the<br />
Community Edition Administrative Console and the command line). Community Edition provides a built-in<br />
security realm called geronimo-admin, which is a properties file realm containing only one user called<br />
system <strong>with</strong> a password of manager, and only one group called admin.<br />
Community Edition also provides a tool in the Administrative Console to configure this in a very easy way.<br />
Clicking on Security -> Users and Groups will open the page illustrated in Figure 8.7 where you can<br />
create or edit a user and a group.
Change language