Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
This is not so much directly related to Perl as it is application development (save that my applications, mentioned soon, are entirely written in Perl). Now that the 'disclaimer' is there, I'll begin:

I have a suite of web-based applications, all performing different tasks of allowing the creation, editing or deletion of 'documents' among other things. Documents is in quotes because all information is really stored in databases and only in metaphor are they actually documents to the end user.

Right now the permission system is patched together -- okay, let me move some code here, change something there, put his name in the code directly over yonder and such. Horrible, I know I should be flogged but a lot of the code was inherited so to speak.

I am re-developing all of the scripts from the ground up and the first thing to change needs to be the access control. But I cannot quite put my finger on a good system or how to implement it. Ultimately, each user should have 'read', 'write', 'edit', 'delete' and/or 'execute' privleges on a number of the applications or documents.

But how to implement, store/retreive permissions in an efficient manner? XML Access Control lists? An application table, detailing who has permissions (comma separated user ids or limited columns?)? User table detailing which applications/documents each individual can access?

So, while I am tackling this issue myself, I am curious as to if and how any of my fellow monks have faced similiar situations.

--
notsoevil
--
Jeremiah 49:32 - And their camels shall be a booty. . .


In reply to Application Access Control by notsoevil

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (3)
As of 2024-04-24 05:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found