No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<html> | <html> | ||
< | <h3> <strong> Access groups </strong></h3> | ||
<p>In this part of MDriven designer sessions access groups have been shown | <p>In this part of MDriven designer sessions access groups have been shown | ||
and how we can use them to authenticate and authorize users. | and how we can use them to authenticate and authorize users. | ||
You probably have different users in your system and these users are probably associated with an access group somehow (ActiveDirectory or something in your application).You will want to allow and disallow user groups to execute actions.This could be done as enable expressions on the Actions – but that would not be very nice since it would kidnap the use of enable from the normal things we use enable for (check data state). Also if a user is never allowed to execute “TheAdminInterface” it might be best to hide that action from view all together. | You probably have different users in your system and these users are probably associated with an access group somehow (ActiveDirectory or something in your application).You will want to allow and disallow user groups to execute actions.This could be done as enable expressions on the Actions – but that would not be very nice since it would kidnap the use of enable from the normal things we use enable for (check data state). Also if a user is never allowed to execute “TheAdminInterface” it might be best to hide that action from view all together. | ||
To facilitate this Modlr has a new concept called <strong> AccessGroups </strong> | |||
Also we have demonstrated how you can continue with the fast pace loop of edit and deploy. | Also we have demonstrated how you can continue with the fast pace loop of edit and deploy. | ||
Line 96: | Line 97: | ||
</script> | </script> | ||
</html> | </html> | ||
Revision as of 19:12, 22 December 2016
Access groups
In this part of MDriven designer sessions access groups have been shown and how we can use them to authenticate and authorize users. You probably have different users in your system and these users are probably associated with an access group somehow (ActiveDirectory or something in your application).You will want to allow and disallow user groups to execute actions.This could be done as enable expressions on the Actions – but that would not be very nice since it would kidnap the use of enable from the normal things we use enable for (check data state). Also if a user is never allowed to execute “TheAdminInterface” it might be best to hide that action from view all together. To facilitate this Modlr has a new concept called AccessGroups Also we have demonstrated how you can continue with the fast pace loop of edit and deploy.