Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
IBM WebSphere Application Server 8.0 Administration Guide

You're reading from   IBM WebSphere Application Server 8.0 Administration Guide Learn to administer a reliable, secure, and scalable environment for running applications with WebSphere Application Server 8.0

Arrow left icon
Product type Paperback
Published in Oct 2011
Publisher Packt
ISBN-13 9781849683982
Length 496 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Steve Robinson Steve Robinson
Author Profile Icon Steve Robinson
Steve Robinson
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

IBM WebSphere Application Server 8.0 Administration Guide
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. WebSphere Application Server 8.0: Product Overview FREE CHAPTER 2. Installing WebSphere Application Server 3. Deploying your Applications 4. Security 5. Administrative Scripting 6. Server Configuration 7. WebSphere Messaging 8. Monitoring and Tuning 9. Administrative Features 10. Administration Tools 11. Product Maintenance Index

Global security


In Chapter 1, WebSphere Application Server 8.0: Product Overview, during the installation process of the WebSphere Application Server, we opted not to turn on global security and thus did not have to supply a password to log in to the Administrative console. We logged in using the username wasadmin and we were not prompted for a password. The truth of the matter is that we could have actually used any name, as the console wasn't authenticating us at all. To protect our WAS from unauthorized access, we need to turn on global security.

Note

It is important to secure the administration of WebSphere, even if the applications being installed are not using security. It is paramount to ensure we have control of our WebSphere environments. The larger your team is, the more important this becomes. In time, other people in your organization will get to know the URLs of your WebSphere servers and, if they are not secured, you cannot really know who is making changes without your approval...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime