Authentication system Database design

Question

1.00/5 (1 vote)

See more:

, +

My Database

Groups:
GroupId,Name

Modules:
ModuleId,Name

ModulePermissions:
ModulePermissionId,ModuleId,PermissionValue,PermissionKey

Approach 1:
GroupModule:
GroupModuleId,GroupId,ModuleId,Permissions(varchar)

Approach 2:
GroupModule:
GroupModuleId,GroupId,ModulePermissionId,isAllowed

Actually i am going to develop a user authentication system for a cms.I am developing an interface where the rights of modules are issued against every Group.
Now i want to know the best practices for the database design for this scenario, since this module would be used for authentication throughout the application , so the application is greatly dependent on these tables.

Let me know if you need more explanation

Posted 1-Aug-15 9:23am

Member 9129971

Updated 2-Aug-15 8:28am

v5

Add a Solution

Comments

PIEBALDconsult 1-Aug-15 15:38pm

What's a "cms"?
Shouldn't there be a user table of some sort?

Member 9129971 1-Aug-15 16:39pm

CMS,Content Management System.This is same like wordpress ,joomla and other cms althought would not have so many functions like these Cms. And there is a User table also ,which has a relationship with Group , these tables are the most important tables they would be use on every request to the server.Specially the GroupModule table is the mostly used table.

Sinisa Hajnal 4-Aug-15 4:48am

Generic advice: optimize your queries, set indexes on join fields, join by integers or other simple types (not varchars), avoid using functions in join conditions or where clause (even TRIM)...other then that, why not create ASP.NET project with membership and copy their design?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)