472,954 Members | 1,485 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,954 software developers and data experts.

security with web-based access

First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?
Jul 20 '05 #1
7 1514
Create two new user logins and assign each login to a specific DB. They
should be SQL authentication and the web application must have the user/pass
specified in the connection string. If the web server is on the trusted
network you shouldn't open any ports in a firewall. You should be set to go.

Rob

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com...
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?

Jul 20 '05 #2
Thanks.

On Thu, 22 Apr 2004 12:25:15 +0200, "Simon Hayes" <sq*@hayes.ch>
wrote:

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com.. .
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?


You might get a better response in an ASP forum (if that's the web platform
you're using), but I can give you some basic answers. The webserver can be a
user - if it uses a domain service account (just like SQL Server), then that
account can be an MSSQL login. In this case, you would have to manage
permissions entirely within your application, as the only account accessing
MSSQL would be the web server service account. Alternatively, some
combinations of web server and browser can impersonate a specific user (I
believe IE/IIS can do this, no idea about other possibilities), so that your
authentication would work as normal.

Simon


Jul 20 '05 #3
Thanks.

On Thu, 22 Apr 2004 14:51:31 GMT, "Rob Wahmann" <ro*@dotcomstudio.biz>
wrote:
Create two new user logins and assign each login to a specific DB. They
should be SQL authentication and the web application must have the user/pass
specified in the connection string. If the web server is on the trusted
network you shouldn't open any ports in a firewall. You should be set to go.

Rob

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com.. .
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?


Jul 20 '05 #4

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com...
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?


You might get a better response in an ASP forum (if that's the web platform
you're using), but I can give you some basic answers. The webserver can be a
user - if it uses a domain service account (just like SQL Server), then that
account can be an MSSQL login. In this case, you would have to manage
permissions entirely within your application, as the only account accessing
MSSQL would be the web server service account. Alternatively, some
combinations of web server and browser can impersonate a specific user (I
believe IE/IIS can do this, no idea about other possibilities), so that your
authentication would work as normal.

Simon
Jul 20 '05 #5
Create two new user logins and assign each login to a specific DB. They
should be SQL authentication and the web application must have the user/pass
specified in the connection string. If the web server is on the trusted
network you shouldn't open any ports in a firewall. You should be set to go.

Rob

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com...
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?

Jul 20 '05 #6
Thanks.

On Thu, 22 Apr 2004 12:25:15 +0200, "Simon Hayes" <sq*@hayes.ch>
wrote:

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com.. .
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?


You might get a better response in an ASP forum (if that's the web platform
you're using), but I can give you some basic answers. The webserver can be a
user - if it uses a domain service account (just like SQL Server), then that
account can be an MSSQL login. In this case, you would have to manage
permissions entirely within your application, as the only account accessing
MSSQL would be the web server service account. Alternatively, some
combinations of web server and browser can impersonate a specific user (I
believe IE/IIS can do this, no idea about other possibilities), so that your
authentication would work as normal.

Simon


Jul 20 '05 #7
Thanks.

On Thu, 22 Apr 2004 14:51:31 GMT, "Rob Wahmann" <ro*@dotcomstudio.biz>
wrote:
Create two new user logins and assign each login to a specific DB. They
should be SQL authentication and the web application must have the user/pass
specified in the connection string. If the web server is on the trusted
network you shouldn't open any ports in a firewall. You should be set to go.

Rob

"Ellen K." <72************************@compuserve.com> wrote in message
news:2p********************************@4ax.com.. .
First of all, I have never done any web-based stuff, so if the
following sounds ignorant, it's because I am!

So far all our SQL Servers are accessed only over our network and we
use Windows authentication. Now the guy I'm working with on the
design of our next stuff wants the two new databases (a transactional
one and my data warehouse) to be additionally accessed by web-based
applications via our company intranet (NOT THE INTERNET). How do we
authenticate under these conditions? The webserver machine will be
talking to the SQL Server ones, i.e. the databases will each be on the
their own separate boxes. Can the webserver be a "user"? If so,
and we want the actual users to have different privileges, then the
web-based apps have to manage that? Or is there a way for the
web-based apps to grab the Windows user and pass it to SQL Server?


Jul 20 '05 #8

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

4
by: Ashish | last post by:
Hi Guys I am getting the following error while implementing authentication using WS-security. "Microsoft.Web.Services2.Security.SecurityFault: The security token could not be authenticated...
1
by: Dave | last post by:
I have a ASP.net application that work fine with IIS 5.0. I'm trying to put it on IIS 6.0. And getting the following error. ASP is enable It is in a virtual directory - I also follow the...
4
by: Henrik Skak Pedersen | last post by:
Hi, I have a set up where a windows client connects to a web service to retrieve a license file. The client is a consumer product which is beeing distributed to multiple locations. 1) I would...
2
by: KaNos | last post by:
Hello world, I've made a webservice (c# v2) to install in a server IIS 6 on a Windows 2000 last SP. We can use the webservice in local, throw the pages wich present the methods, with a windows...
1
by: WebServiceSecurity | last post by:
The issue involves the following technologies: - 1. .NET 2.0 Framework 2. WSE2.0 (WS-Security) 3. X.509 certificates 4. BEA Weblogic 8.1.5
0
by: alf | last post by:
I have an app that was running in my local server using full trust, now I moved it to hosting company wish run in Medium trust. Then I get a Security exception (details below) Then I configured...
4
by: confused1234 | last post by:
I get the error at the bottom of this post when i click on a linkbutton, javascript:__doPostBack('ctl00$Main$btnchangeemail','') The problem is intermitant, sometimes it works and sometimes...
1
by: =?Utf-8?B?TWFuanJlZSBHYXJn?= | last post by:
Hi I am creating a web service PreprocessingService with IIS Hosting and transport layer security with user name and password. I created a self-signed certificate IISHost in IIS which is issued...
2
by: Nathan Sokalski | last post by:
When I call System.Web.Security.Roles.GetRolesForUser() it returns no results even though I have roles associated with the currently logged in user. I am able to get the username by calling...
5
by: VictorG | last post by:
Hello, I am trying to secure a webservice using WSE 3.0 and the turnkey usernameForCertificateSecurity profile. I am passing a valid username token, and on the server I have overridden the...
0
by: lllomh | last post by:
Define the method first this.state = { buttonBackgroundColor: 'green', isBlinking: false, // A new status is added to identify whether the button is blinking or not } autoStart=()=>{
2
by: DJRhino | last post by:
Was curious if anyone else was having this same issue or not.... I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
2
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM) The start time is equivalent to 19:00 (7PM) in Central...
0
by: Aliciasmith | last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
0
tracyyun
by: tracyyun | last post by:
Hello everyone, I have a question and would like some advice on network connectivity. I have one computer connected to my router via WiFi, but I have two other computers that I want to be able to...
2
by: giovanniandrean | last post by:
The energy model is structured as follows and uses excel sheets to give input data: 1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
1
by: Teri B | last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course. 0ne-to-many. One course many roles. Then I created a report based on the Course form and...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM) Please note that the UK and Europe revert to winter time on...
1
by: GKJR | last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.