Part 9 MDriven Turnkey, cloud tools and access groups
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<html> | <html> | ||
<p> | <h4> <strong> Access groups </strong></h5> | ||
<p>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. | |||
Also we have demonstrated how you can continue with the fast pace loop of edit and deploy. | |||
<style> | |||
p { | |||
text-align: justify; | |||
width: 90% | |||
} | |||
</style> | |||
</p> | |||
<p1> | |||
<em>To make your experience more comfortable, we set the main tags mentioned in the video to the right bar menu of this mini player. Choose the interesting subtitle on the list and immediately get to the exact theme timeplace in the video. Now you can pick any topic to be instructed without watching the whole video.</em> | <em>To make your experience more comfortable, we set the main tags mentioned in the video to the right bar menu of this mini player. Choose the interesting subtitle on the list and immediately get to the exact theme timeplace in the video. Now you can pick any topic to be instructed without watching the whole video.</em> | ||
<style type="text/css"> | <style type="text/css"> | ||
p1 { | |||
opacity: 0.7; | opacity: 0.7; | ||
text-align: justify; | text-align: justify; | ||
| Line 13: | Line 25: | ||
} | } | ||
</style> | </style> | ||
</ | </p1> | ||
<style> | <style> | ||
#video12 { | #video12 { | ||
| Line 55: | Line 67: | ||
<div> | <div> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="69" tabindex="0"> MDriven turnkey | ||
</span> | </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="90" tabindex="0"> Cloud connection tool </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="246" tabindex="0"> License and ticket site </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="326" tabindex="0"> Viewmodel named index </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="516" tabindex="0"> MDriven designer snippets </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="546" tabindex="0"> <strong> ASPNETIdentity.snippets:</strong> </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="648" tabindex="0"> • Apply snippet dialogue </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="787" tabindex="0"> • SysUser </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="805" tabindex="0"> • SysSingleton </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="1029" tabindex="0"> MDriven server persistence </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="1289" tabindex="0"> Authentication on the site </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="1379" tabindex="0"> <strong> Access Groups of users:</strong> </span> | ||
<span data-video="yDKHzI992jQ | <span data-video="yDKHzI992jQ" data-start="1479" tabindex="0"> • Actions controlled by access groups </span> </div> | ||
</div> | </div> | ||
| Line 84: | Line 96: | ||
</script> | </script> | ||
</html> | </html> | ||
= '''Access groups''' = | |||
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. | |||
Revision as of 19:10, 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. Also we have demonstrated how you can continue with the fast pace loop of edit and deploy.
MDriven turnkey
Cloud connection tool
License and ticket site
Viewmodel named index
MDriven designer snippets
ASPNETIdentity.snippets:
• Apply snippet dialogue
• SysUser
• SysSingleton
MDriven server persistence
Authentication on the site
Access Groups of users:
• Actions controlled by access groups
Access groups
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.
This page was edited 93 days ago on 02/10/2024. What links here