Security can be assigned to any object generated by the instance or to any WebPanel that has WorkWithPlus applied.
In order to check if certain user has access to an object with security, WorkWithPlus inserts the verification code in the MasterPages that are specified within WWPConfiguration.
The verification code is the following:
This can be set to all the master pages of the application like the example above, or you can specify to which MasterPages you want the security verification code to be inserted.
If some object doesn't have a MasterPage assigned (property MasterPage is '(none)'), or has assigned a MasterPage that is not included in MasterPages with security (image above), the verification code will be set to the object itself.
Security can be assigned to any object generated by the instance. This is set by the property "Security Functionality Key" of each object.
Its default value (<default>) will check if one of the roles associated to the logged user have permission to access the Fucntionality set as the Instance's main functionality. This Functionality key is set in main node.
All the objects within the transaction that has the <default> value, or has the same value will be grouped into one Fuctionality so that when administrator grants access so some functionality it will grant permission to access to all the objects associated to that functionality. This also occurs to all objects within the application that has assigned the same value in its Security Functionality Key.
Security can be assigned to any WebPanel that has WorkWithPlus Pattern applied. This is set by the property "Security Functionality Key".
Developer could set any Functionality key to this WebPanel, could set an existing one in order to group it in some Functionality or a new one.
If this property is empty, the object will not be associated to any security functionality, so this WebPanel has no security and everybody will have access to it.
It is important to have in mind that every time that we change some 'Security Functionality Key' and we want to impact these changes in the application at runtime, we have to follow the steps of the section Update Security Functionalities of Advanced Security:Update Advanced Security Funcionalities
|