Access control requires two things: authentication and authorisation. Apache can do basic and digest authentication (authentication), and Apache can control which user can access which script (authorisation). Both of these can be configured via htaccess.

If that authorisation isn't fine grained enough for you (i.e. you want to control access to records, not to urls), you can do the autorisation in the Perl script by grabbing the authenticated user from $cgi->remote_user.

You could also do the authorisation yourself if you wish to wish to allow users to logout or become other users. This is a bit more involved since it requires maintaining a state over multiple requests. This is usually done using a session.

In reply to Re: Restricting Access by ikegami
in thread Restricting Access by Perobl

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.