Last updated by
2 years ago
Page: Shiro Release Notes, Version:16
Version 1.1
- SHA-256 is now used by the default credential matcher
- New ShiroSecurityService that can be used to encode passwords with the same hash algorithm as the configured credential matcher
- Uses the 1.1 release of Apache Shiro
- Renamed
quick-startcommand toshiro-quick-start* Realms can implement theorg.apache.shiro.authc.LogoutAwareinterface and be notified of when the user logs out - the
security.shiro.filter.configsetting is deprecated in favour ofsecurity.shiro.filter.filterChainDefinitions+ other configuration options. It will continue to work though.
Breaking changes
-
WebUtilsandSavedRequest(used in the recentAuthControllertemplates) have moved from theorg.apache.shiro.webpackage toorg.apache.shiro.web.util - shiroSecurityManager no longer has a
login()method, soAuthControllershould useSecurityUtils.subject.login()instead
Version 1.0
- These are changes from the last version of the JSecurity plugin*
- Configuration settings now start
security.shirorather thanjsecurity. - Except
jsecurity.legacy.filter.enabledwhich is nowsecurity.shiro.annotationdriven.enabled. - All
org.jsecuritypackages are noworg.apache.shiro. - New
create-wildcard-realmcommand that creates a database realm based on Shiro's wildcard string permissions. This is simpler than the old DB realm. - Access control by convention now uses wildcard permissions rather than
JsecBasicPermission. - You can now configure an alternative login URL that the plugin will redirect to:
security.shiro.redirect.uri. - You can now override the default permission resolver, remember me manager and authentication strategy by defining your own beans with the appropriate names (
shiroPermissionResolver,shiroRememberMeManager,shiroAuthenticationStrategy). - Implemented GRAILSPLUGINS-627: you can now protect URLs using Shiro's standard
FormAuthenticationFilter. - Fixed GRAILSPLUGINS-869: HTTP Basic authentication no longer throws an exception for an empty username or password.
- The
quick-startcommand now creates a wildcard permission based database realm, although it has the default nameShiroDbRealmwhen installed.
AuthController class generated from an earlier version of the Shiro or JSecurity plugins:
this.securityManager.login(authToken)SecurityUtils.subject.login(authToken)