Releases: Servoy/svySecurity
2024.3.0
v2022.3.0
Enhancements
| Case | Description |
|---|---|
| SVYX-262 | svySecurity is always creating sample data |
| SVYX-290 | Low performance when having 100+ permissions / roles |
| SVYX-195 | adding toString method |
| SVYX-179 | Kill Security Console |
Fixes
| Case | Description |
|---|---|
| SVYX-215 | SSO does not work |
| SVYX-252 | Increase in field length not reflected in scope |
| SVYX-458 | SvyProperties delete commits all outstanding changes |
Release v1.6.0
Servoy Security 1.5.0
Enhancements
| Case | Description |
|---|---|
| SVYX-76 | Tenant should not be able to lock themselves! |
| SVYX-143 | SvySecurity: Support JWT-based Authentication |
| SVYX-51 | Control single sign on for multiple solutions |
| SVYX-176 | Added Tenant & User UUID (to make some linking easier) |
| SVYX-182 | Increase length of username field in DBI |
| SVYX-187 | SvySecurity: Add startup args to logout method |
Servoy Security 1.4.2 release
Minor update for Servoy 2020.09 with the following fix:
- Fixed an issue where a saveRecord() or deleteRecord() in svySecurity would save all other open changes
Servoy Security 1.4.1 release
Minor update for Servoy 2020.09 with the following fixes:
- #23 Bug function loadProperties
- SVYX-95 Warning on deprecated components for svySecurityUX
Servoy Security 1.4.0 release
Enhancements in svySecurity API
- #10 sync permissions run to often
- syncPermissions when creating sample data
- Throw errors when editing roles of a master Tenant and the user is logged in
- Generate warning when editing roles of a master or slave tenant while logged in as an user
Enhancements in svySecurityUX
- Fix svySecurityUX Roles list not updated when a new role is created
- Show Master-Slave info for logged Tenant
Enhancements in svySecurityConsole
- Added sync permission button to svySecurityConsole
Breaking Changes
Security permissions are synchronized at every user login for the deployed solution. Such default behavior is setup to facilitate your testing and your first deployment, however synchronizing permissions at every login can impact the perfomances of your solution. Is recommended to use a postImportHook module running scopes.svySecurity.syncPermissions() to synchronize permissions at every deployement instead and disable auto-sync for every login. Auto permission sync can be disabled by setting the user property svy.security.auto-sync-permissions-when-deployed=false.
Servoy Security 1.3.0 Release
This release contains new module and several enhancements to the Security modules
Behavior Changes
- Permisssion will be synced only in Developer. To sync permissions at deployment use a post-import hook
Enhancement to svySecurity module
- Tenant can be created as slave of existing tenant. Master tenant will propagate to all it's slave tenants changes to it's roles and to the role's permissions. e.g. every new role created in a master tenant will be created in all it's slave tenants.
- New APIs cloneTenant(tenantToClone, name, makeSlave);
- New Tenant's API createSlave(name), getSlaves(), isMasterTenant();
- New (optional) email field added for the user. User have new API getEmail()/setEmail();
- New session API getSolutionName()
- Permission will be synced only in the Developer
- Tenant table filters includes null value for tenant_name
- SecurityBatch starting in developer is now optional
New svySecurityUX module v1.3.0
New svyProperties module v1.0.0
Servoy Security 1.2 Release Candidate 2
- added solution name to info tracked by sessions
- Added Session.getSolutionName() to API
- added system flag to skip cleanup of abandoned sessions when in developer (Set user.cleanSessionsInDeveloper=false in servoy.properties)
Servoy Security 1.2 Release Candidate 1
Deprecates client ping in favor of server-side batch to "clean-up" abandoned sessions
NOTE: Session.getLastActivity is deprecated