Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Spring Security - Third Edition

You're reading from  Spring Security - Third Edition

Product type Book
Published in Nov 2017
Publisher Packt
ISBN-13 9781787129511
Pages 542 pages
Edition 3rd Edition
Languages
Authors (3):
Mick Knutson Mick Knutson
Profile icon Mick Knutson
Peter Mularien Peter Mularien
Profile icon Peter Mularien
ROBERT WILLIAM WINCH ROBERT WILLIAM WINCH
Profile icon ROBERT WILLIAM WINCH
View More author details

Table of Contents (19) Chapters

Preface 1. Anatomy of an Unsafe Application 2. Getting Started with Spring Security 3. Custom Authentication 4. JDBC-Based Authentication 5. Authentication with Spring Data 6. LDAP Directory Services 7. Remember-Me Services 8. Client Certificate Authentication with TLS 9. Opening up to OAuth 2 10. Single Sign-On with the Central Authentication Service 11. Fine-Grained Access Control 12. Access Control Lists 13. Custom Authorization 14. Session Management 15. Additional Spring Security Features 16. Migration to Spring Security 4.2 17. Microservice Security with OAuth 2 and JSON Web Tokens 18. Additional Reference Material

Cross-Site Scripting 

XSS attacks involve malicious scripts that have been injected into a trusted site.

XSS attacks occur when an attacker exploits a given web application that is allowing unventilated input to be sent into the site generally in the form of browser-based scripts, which are then executed by a different user of the website.

There are many forms that attackers can exploit, based on validated or unencoded information provided to websites.

At the core of this issue is expecting a user to trust the site's information that is being sent. The end user's browser has no way to know that the script should not be trusted because there has been an implicit trust of the website they're browsing. Because it thinks the script came from a trusted source, the malicious script can access any cookies, session tokens, or other sensitive information retained by...

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 $15.99/month. Cancel anytime}