What I would generally do is this:
First, shove the entire authentication/authorization problem off to LDAP (OpenDirectory), where it properly belongs in any organization of any size. :-) Apache/Nginix can interrogate those credentials to grant or to deny access on a site-basis. (It can also make the user’s authenticated identity and authorized credentials known to the web application.) IIS is especially good at this.
Second, use redirects to send the user to a locally-defined destination such as, say, www.appname.mycompany.com. Or some appropriate intra-net location. Set up each application, more or less as-is, in each place.
Yeah, you’re darn right ... you passed the buck.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||