Well, one way to handle the authentication requirements of a web-site, in an LDAP-based intranet environment, is to simply let the web server protect the entire site. Both Apache and (especially...) IIS can do this. The web server has the magical means to determine who the requesting internal user is, and of course to distinguish internal users from outsiders. Unauthorized users simply can’t reach the site at all. Furthermore, those that do, have available credentials that the CGI program can query if further authentication logic within the site needs to use it. (Internet users are automatically excluded.)
This is one key way in which “intra-net” web sites are able to play by very different and much-simplified rules, versus those of the “wild and wooly” Internet-at-large. If you simply want to restrict the entire site, you don’t have to write protective logic into the site at all. The site is inside the fortress, and they’re checking badges at the door, and there’s no other way to get inside, and ... and that’s it. (“Schweet!”)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||