Vaadin 7 on Grails 2.x
  • Introduction
  • Project setup
    • Command Line
    • IntelliJ IDEA
    • Eclipse
    • NetBeans
    • Plugin Configuration
    • Clean up
    • Best Practices
  • Database
    • GORM
      • Create Domain Model
      • Transactions
      • LazyInitializationException
      • Open Session In View I.
      • Open Session In View II.
      • Table Container
    • Groovy SQL
      • Create Sql
      • Execute SQLs
    • MyBatis
      • Configuration
      • Basics
    • JdbcTemplate
      • Create Beans
      • Usage
    • Clean Up With Alternatives
  • Architecture
    • Model View Presenter
  • Spring Autowiring
    • Create Simple Application
    • Application With Navigator
  • UI
    • Re-using GORM Validations
    • Async Push
    • Multiple application
    • SASS Compilation
    • Widgetset Compilation
  • Spring Security
    • Spring Security Dependency
    • Spring Security Basics
    • Secured Navigator
  • Localization
    • Localization Basics
    • Custom MessageSource
  • REST
    • Without using root URL
    • Using root URL for Vaadin app
  • Plugin development
    • Github
    • Development
Powered by GitBook
On this page

Was this helpful?

Spring Security

PreviousWidgetset CompilationNextSpring Security Dependency

Last updated 5 years ago

Was this helpful?

Spring Security in pure Grails application, where no Vaadin is involved, is provided by plugin, because if we work with pure Grails, the controllers are the end points and we can define security at that level, by adding Spring security annotations. This is not case for Vaadin application.

In Vaadin applications we use Navigator instead of Grails controllers or we render different UI components based on user's roles. In this chapter we will explore way to do using .

spring-security-core
Spring security framework