Protected Configuration with Desktop Apps in .Net

If you are looking for a solution to use .Net 2.0 Protected Configuration feature with Windows application rather than Web apps, check out my article at codeproject.


http://www.codeproject.com/KB/security/ProtectedConfigWinApps.aspx

Comments

Post a Comment

Popular posts from this blog

Prevent site owners from creating subsites in SharePoint 2010

Image
If your users are naughty enough and you want to keep them from adding new sub sites for a specific web application. Just follow the steps below: This is specially useful when the naughty users are site owners such as in case of My Sites. 1. From Central Administration, Go to “Manage Web Application” screen. 2. Select a web application and click the “Permission Policy” button from the ribbon. 3. A screen will pop up with all existing permission levels. 4. Select “Add Permission Policy Level” link from the screen. 5. On “Add Permission Policy Level” screen, name the permission level appropriately. 6. Under Site Permissions category, select the “Deny” option for “Create Subsites” permission and save it. 7. You will see a new Permission Policy Level in the list of existing ones. 8. From the ribbon, click “User Policy” button. 9. A screen will pop up with all existing user policies. 10. Click “Add Users” link from Policy For Web Application screen. 11. A wizard will open, allowing you to s...
Read more

PowerApps Form for SharePoint and Access Denied Errors

Image
Error When using SharePoint's Online's customise form option to create PowerApps forms, we may encounter the error below: An error occurred on the server. Server Response: Access denied. You do not have permission to perform this action or access this resource.  This is often caused by lack of permissions on underlying lists. Scenario I was using multiple list data sources in a single PowerApps list form. Form had staged input screens for related data and a group of end users was not allowed access to the list corresponding to the last stage of input. Nonetheless, when the form opened for any user, PowerApps was trying to load all the data sources resulting in above error. The Fix I could conveniently fix the error by granting at least read-only access to end users on all lists. However, the list causing error had confidential data only restricted to few users.    An easy fix is to add an empty folder, break it's inheritance and assign less privi...
Read more