OnSolutionOpen and firstForm are loaded and run before the security table filters are set

[SteveHawes]

If you have an onSolutionOpen method this gets run before the initSession() and filterSecurityTables() in the svySecurity module. This could cause data leakages as the tables will not be filtered correctly at that point.

Also whatever is set as the first form is also loaded and shown before the initSession() and filterSecurityTables() methods so again this could cause data leakage.

Another side effect is that you cannot use the scopes.svySecurity.active_tenant, active_user or active sessions relations in the first form onLoad method.

[seanthomasdevlin]

Hi Steve,

Thanks for your feedback on SvySecurity.
Which approach do you take? Login Form or Login Module ?
The latter is recommended based on your needs.

[SteveHawes]

I was just playing with the module to see how it is developing following the webinar recently. I think it could really benefit from better integration with the built in tenant options and I can see that there is already a ticket relating to this. I found that if you call security.setTenantValue immediately prior to calling security.login in svySecuriy.login then everything works as I would expect and the filters are applied prior to everything loading. Obviously you would need to remove this filter if the login fails. I also don’t see why the tables in the svy_security database don’t use the tenant flag for the tenant_name columns. Just my 2 cents worth on how I think the module could be improved. Thanks Steve

…

Sent from my iPhone

On 12 Feb 2020, at 18:59, Sean ***@***.***> wrote:  Hi Steve, Thanks for your feedback on SvySecurity. Which approach do you take? Login Form or Login Module ? The latter is recommended based on your needs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[seanthomasdevlin]

Hi Steve, yes that is planned for next release documented in another case.

Thanks