Constructor Detail

• ComponentBasedConfigBlender()

Method Detail

• static InMemoryUserDetailsManager bridgeSpringSecurityUserProperties(java.lang.String userName, java.lang.String userPassword, java.util.List<java.lang.String> userRoles)

  If spring.security.user.name (and optionally spring.security.user.password / spring.security.user.roles) are set, returns an InMemoryUserDetailsManager containing that single user, mimicking what Spring Boot's UserDetailsServiceAutoConfiguration would have created had it not been excluded by SecurityAutoConfigurationExcluder.

  Defaults follow Spring Boot's defaults:

  • password - user (literal)
  • roles - [USER]

  The returned manager is intended to be combined with chainUserDetailsServices so it coexists with the plugin's primary userDetailsService. Returns null if spring.security.user.name is not set.

  Parameters:

  userName - the resolved spring.security.user.name value

  userPassword - the resolved spring.security.user.password value (may be null)

  userRoles - the resolved spring.security.user.roles value (may be null)

  Returns:

  the bridged InMemoryUserDetailsManager, or null if the bridge is not applicable

• static UserDetailsService chainUserDetailsServices(ApplicationContext applicationContext, UserDetailsService primaryUserDetailsService)

  Wraps the plugin's primary UserDetailsService bean in a chain that also queries every other user-defined UserDetailsService bean in the application context. The plugin's bean is queried first; user beans are queried in bean-name order if the plugin's bean throws org.springframework.security.core.userdetails.UsernameNotFoundException.

  This method does not modify the plugin's bean directly. Instead it returns a UserDetailsService that callers can substitute in their authentication providers if they want the chained behaviour. The Grails plugin core does not currently rewire its providers to use the chained UDS automatically; users who want this behaviour should declare the returned service as a bean and reference it via grails.plugin.springsecurity.dao.userDetailsService (or the provider-specific equivalent).

  Parameters:

  applicationContext - the application context to scan

  primaryUserDetailsService - the plugin's primary userDetailsService bean (typically GormUserDetailsService)

  Returns:

  a chained UserDetailsService, or the primary unchanged if no other user beans are present

• static int mergeUserAuthenticationProviders(ApplicationContext applicationContext, ProviderManager authenticationManager)

  Adds user-defined AuthenticationProvider beans to the plugin's ProviderManager. User providers are appended so that the plugin's primary providers (typically the GORM-backed DAO provider) are tried first.

  Providers already present in the manager (for example, those declared via grails.plugin.springsecurity.providerNames) are not re-added.

  Parameters:

  applicationContext - the application context to scan

  authenticationManager - the plugin's authenticationManager bean (a ProviderManager)

  Returns:

  the number of user providers merged

• static int mergeUserSecurityFilterChains(ApplicationContext applicationContext, java.util.List<SecurityFilterChain> pluginChains)

  Adds user-defined SecurityFilterChain beans to the plugin's filter chain list. User chains are prepended (higher precedence) because their request matchers are typically more specific than the plugin's catch-all chain.

  The plugin's own chains are not registered as named beans (they are appended directly to securityFilterChains in SpringSecurityUtils.buildFilterChains), so every SecurityFilterChain bean visible to the application context is treated as user-defined.

  Parameters:

  applicationContext - the application context to scan

  pluginChains - the plugin's mutable securityFilterChains list (the same list the plugin's FilterChainProxy references)

  Returns:

  the number of user chains merged