Releases
4.0.0
Compare
Sorry, something went wrong.
No results found
introduced API-Interfaces for Resources to allow internal call without http
keyValue api-change
key is now more flexible "Allowed key chars are a-Z, 0-9 and _-.#"
no value length limit to allow flexible json-values (dto's have now some common jackson-readers)
key with # prefix will not be part within jwt-token (similar to _) but will get returned when fetching user-info (or /me endpoint)
prefixed jpa entities/tables with co_
user -> co_user
user_roles -> co_user_roles
user_keyvalue_pairs -> co_user_keyvalue_pairs
you need to perform with manually before starting your application after upgrade!
jpa: removed fetch.EAGER to improve performance when used entity as relations
monitoring
merged events and added some new for impersonate, refresh + requestMe...
added ActiveUserStore to track current active users
mailing
upgraded to new emai-template-builder with new theme of postmark
upgraded to new email-templates and improved configurations for logo
refactor: removed spring-boot-starter-mail + introduced EmailSender interface and refactored tests by this step
introduced extra module commons-auth-email-smtp to allow default config for spring-boot-starter-mail
added postmark sender als alternative to smtp version
added EmailChangeEvent + UsernameChangeEvent
fix: never set avatar to null when avatarService is active
introduced JwtTokenStore-Interface to allow different implentation for refreshing accessToken (default http/optional internal service)
refactored many services with some internal breaking changes
upgraded spring-boot 2.3.4, guava 29.0, jjwt 0.11.2, passay 1.6.0 + commons-rest 2.0.5
You can’t perform that action at this time.