Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2003-02-27 : 07:38:35
|
Mike writes "This has been something that has been bugging me for quite some time now. If anybody has seen how things work at the easyeverything internet cafe chain then they may have a better idea of how things are donebasically at the internet cafe each client is reimaged for every user and automatically logged on to a local user accountnow here comes the interesting part!user is not allowed any other outbound internet requests until logged and authorised against a sql table of usernames and then own password has been created = if not authorised everything is redirected to login pageonce logged in there is a heartbeat maintained between each client and the main sql boxes that then monitors session credit etcetci was just wandering how they would have managed to write an app that doesnt allow anything out until logged against sql through asp pageplease maybe you guys could help shed light" |
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-02-27 : 07:43:07
|
They simply set up their web servers to validate against the SQL Server data and reject any HTTP request that doesn't pass. There's nothing a SQL Server can do to restrict internet access on its own, it's not a network manager...it would have to work in concert with the routers, firewalls, and other components of the internet transfers being handled through their system. |
|
|
Andraax
Aged Yak Warrior
790 Posts |
Posted - 2003-02-27 : 08:49:17
|
They are probably using some kind of Proxy Server which all traffic is routed through. Many proxy servers (including the Microsoft ISA server) allows for different sorts of authentication for outbound surfing. At our company the users are validated against a RACF database on the mainframe. |
|
|
|
|
|