Hi,
Our Portal application currently uses a legacy user database, that
contains the user definitions, roles and access rights.  This has 2
disadvantages :
- system administrators need to add users in two databases (NT Domain user
database and the Portal legacy user database)
- all communication is done via http, not via https
Now the question ?
What is the best way to 'hook' our Portal application in our customers'
web server environment ?  Is every other application also using its own
user database (like e.g. Oracle), or is anyone relying on the Operating
System user database ?  Is LDAP already widespread enough to be used for a
company-wide user database ?
What does it take to use the https protocol ?  Is this purely a problem of
the person installing and maintaining the web server (thus our customer),
or must this be maintained by the Web application (so it becomes our
problem) ?
What is an efficient way to enable https on a MS IIS server or MS PWS
server ?  Is the registration of a key (?) with Verisign (I think)
something that is free, or does this require some kind of [paid]
subscription ?
And finally, if the user authentication is handled by JRun, how can the
web application invalidate (log out) a user ?  Is the user not
automatically re-authenticated on the next request (without a login popup)
?
Thanks.

--- 
NEED TECHNICAL TIPS, TOOLS, AND INSIGHTS?  Is FREE okay?
Visit EarthWeb for the latest in IT Management, Software Development, 
Web Development, Networking & Communications, and Hardware & Systems.  
Click on http://www.earthweb.com for FREE articles, tutorials,
and discussions from the experts.
---
You are currently subscribed to pro_java_server as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-pro_java_server-$subst('Recip.MemberIDChar')@p2p.wrox.com