Hi,
I'm not sure this is the right group to post this message but....
What would it take Regarding Resources & Technology
to shift a public website to a secure private one that only authorized users
can enter, after they have entered their Credit card Info ?
thanks in advance
Romy
"romy" wrote in message news:umxscHf$EHA.2192@TK2MSFTNGP14.phx.gbl...
: I'm not sure this is the right group to post this message but....
:
: What would it take Regarding Resources & Technology
:
: to shift a public website to a secure private one that only authorized
users
: can enter, after they have entered their Credit card Info ?
Probably not ASP DB related but consider you will probably need a
certificate for an SSL connection for starters and a merchant account or two
or First Pay which can take the payment for you, which will eliminate the
need for a certificate and an SSL connection, and/or PayPal account to
accept payments, etc..
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp
On Wed, 19 Jan 2005 08:39:35 +0200, "romy"
wrote:
>I'm not sure this is the right group to post this message but....
Probably not, but I'm not sure where it would go. Maybe the IIS
groups.
>What would it take Regarding Resources & Technology
>
>to shift a public website to a secure private one that only authorized users
>can enter, after they have entered their Credit card Info ?
A method of accepting credit card payments and a method of authorizing
users. There are dozens of credit card options, and authentication
can be Windows based or you could roll your own in a database.
Jeff
Well at least as a part of the whole perhaps have a login page that asks
the user for his username and password. And whatever page that posts to
(which could be the same page for a self posting form) tests these
fields against what is in the database, sets the username and userlevel
session variables accordingly, and then redirects to the proper page -
i.e. back to the login page if the password is wrong (perhaps with a
JavaScript popup saying wrong username/password combination) or to the
main menu page if the password is correct:
Session("UserName") = objRS("UserName")
Session("UserLevel") = objRS("UserLevel")
Response.Redirect "mainmenu.asp"
Then you can use If Then's or Select Case on each page to control
whether a user is allowed to actually be there and whether particular
links of where a user can go actually show up.
If (Session("UserLevel") <> "Admin") And (Session("UserLevel") <>
"Regular") Then
Response.Redirect "login.asp"
End If
And to see something like this in action you can do the following:
- Go to http://www.bullschmidt.com/login.asp (the ASP Web database
demo's login page)
Best regards,
J. Paul Schmidt, Freelance ASP Web Developer
http://www.Bullschmidt.com
ASP Design Tips, ASP Web Database Demo, Free ASP Bar Chart Tool...
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!