DynamicData: Database Based Permissions - Part 1(csharpbits.notaclue.net)

submitted by MIT560MIT560(102) 8 months, 22 days ago

Found this a great read for those who wish to apply Table or even Column level Permissions to a Dynamic Data application. The Author has spent a great deal of time getting to know and help others in the ASP.NET Dynamic Data community.

1 comment |category: |Views: 19

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by dpetersondpeterson(4397) 8 months, 23 days ago 0

It seems like a clever solution, however I'm not so sure that it *should* be necessary. I'm guessing that the reason for this solution is that most web applications would pool only a set number of database connections, all under the same login, rather than a connection per user. A connection per user would allow the application to let the database handle permissions itself (it can do table/column permissions). However there is significant overhead in opening a new database connection for each user.
Perhaps the problem lies with SQL Server logins. SQL Server logins tie all security to the login, rather than the session. Meaning, I can't change security contexts on an open connection. I have to re-establish the connection under different credentials.

Reply

information Login or create an account to comment on this story