Showing posts with label authentication. Show all posts
Showing posts with label authentication. Show all posts

Saturday, March 31, 2012

The ASPNET Sql Server Account

What's the proper way to setup this account in SQL Server?

We're using Windows authentication on our network and to give any user permission in the database I have to grant it to the ASPNET account. This seems to defeat the purpose of using Windows authentication because anyone that opens the ASP.NET page will have those rights in the database even if they aren't listed as a user in the DB.

For example, I give read-only rights to the ASPNET account and even if I give an individual user db_datawriter rights, they still cannot write to the DB unless I grant the ASPNET account db_datawriter rights. Then anyone can save/modify the data.Is SQL server installed on the same machine as IIS?

This will have an impace on how the ASPNET user operates.
Both are on the same machine.
set impersonation on in the web config file

<impersonate=true/>

Or something to that affect...
This is a good article on the microsoft site, it explains the different methods for accessing SQL server.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbconaccessingsqlserverfromwebapplication.asp

This is also a good article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;815154
Originally posted by hellswraith
set impersonation on in the web config file

<impersonate=true/>

Or something to that affect...

that did the trick. well actually it was

<identity impersonate="true" />

then you can get rid of the ASPNET account if using Windows authentication.
Does anyone know if this impersonate would work if IIS and SQL server are on different machines.
I have a feeling it won't but I am happy to be told I am wrong.
I'm pretty sure they have to be on the same machine. I think I read that on MSDN.
That was my understanding. The first article in on of my previous posts talks about it.
Sometimes I wonder if I understand it the way they mean it.
From my interpretation of the article, You need to have the SQL Server and IIS (web server) on the same machine if you want to use Windows authentication OR anonymous access with the ASPNET account.

If you want to access the SQL Server using a Mapped Windows Domain User or prompting for the username and password and passing them as credentials then you don't need the SQL Server and web server on the same machine.
I went on ASP.NET training last week where IIS and SQL were on the same server, the ASPNET account was used.
We came away thinking that is how it naturally worked. It took me half a day and some searching to find out it wasn't so cut and dried.

the authentication process of personalization-profile configuration

hi, recently, i came to study asp.net 2.0, and met a problem like this.

the proflie property can let user briefly and conveniently to create personalization properties in actual use, which change the traditional

approach.but because of the personalization, profile property should set authorization and authentication configuration first. and when the

visitor do not login, asp.net has supplied a solution to resovle the situation, after simply setting the configuration <anonymousIdentification

enabled ="true"> , asp.net can record the personalization information for the anonymous visitor automatically. but what, i wonder to konw,

asp.net had done for us? how it can get the indentification of the visitor and make distinction between visitors,and what had

happened to make it possible?

Anonymous user is the one who is not logged in (so it wont bother for asp.net either its you or me, both are anonymous). When a user is not logged in and if the anonymousIdentification is set to true, the AnonymousUserTemplates will be shown as well as AnonymousProfile information. Profile will track individually only of those whose membership was created.

Thanks


thank you for your reply! best wish to you from the east!


Good Luck!

Thanks

-- mark the thread as resolved, if this post answers you!

Tuesday, March 13, 2012

the membership of asp.net2.0 is useful in my case?

Membership is purely for authentication. For extra user data you should look
into the Profile.

-Brock
DevelopMentor
http://staff.develop.com/ballen

> the membership asp.net2.0I have many User attributes like telephone
> number,
> security ID, Country etc...
> I must retrive these attributes after the user login.
> How can I save do with the membership of asp.net2.0?Adding that I have yet to come to understand the scope of the current
aspnetdb.mdb database schema and hope somebody who knows what the heck all
those columns actually mean and what they can be used for will document it
and doing it yesterday will not be soon enough for me.

--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/

"Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
news:453106632490060869625168@.msnews.microsoft.com ...
> Membership is purely for authentication. For extra user data you should
> look into the Profile.
> -Brock
> DevelopMentor
> http://staff.develop.com/ballen
>
>> the membership asp.net2.0I have many User attributes like telephone
>> number,
>> security ID, Country etc...
>> I must retrive these attributes after the user login.
>> How can I save do with the membership of asp.net2.0?
>>
Well, I'd agree. It'd be nice to have these documented, but on the other
hand that's somewhat going against the idea of a provider (wether it be membership
or profile). IOW, it's a black box of functionality. It's academically interesting
to understand them, but too much info is a bad thing as one tends to want
to modify things when you shouldn't. If you don't like their implementation,
you can create your own Membership or Profile provider that works with all
the UI controls just the same as the built in providers from Microsoft.

-Brock
DevelopMentor
http://staff.develop.com/ballen

> Adding that I have yet to come to understand the scope of the current
> aspnetdb.mdb database schema and hope somebody who knows what the heck
> all those columns actually mean and what they can be used for will
> document it and doing it yesterday will not be soon enough for me.
> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
> news:453106632490060869625168@.msnews.microsoft.com ...
>> Membership is purely for authentication. For extra user data you
>> should look into the Profile.
>>
>> -Brock
>> DevelopMentor
>> http://staff.develop.com/ballen
>>> the membership asp.net2.0I have many User attributes like telephone
>>> number,
>>> security ID, Country etc...
>>> I must retrive these attributes after the user login.
>>> How can I save do with the membership of asp.net2.0?
Its not a matter of like or dislike. I can't dislike something simply
because I do not understand it. Its after I come to understand something
that I can make a reasonable determination.

I'm confident the schema will be documented and many articles will appear --
eventually -- but again, yesterday would not have been too soon for me.

Where is Dino Esposito et. el. when you really need them? ;-)

--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/

"Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
news:460338632490389934897792@.msnews.microsoft.com ...
> Well, I'd agree. It'd be nice to have these documented, but on the other
> hand that's somewhat going against the idea of a provider (wether it be
> membership or profile). IOW, it's a black box of functionality. It's
> academically interesting to understand them, but too much info is a bad
> thing as one tends to want to modify things when you shouldn't. If you
> don't like their implementation, you can create your own Membership or
> Profile provider that works with all the UI controls just the same as the
> built in providers from Microsoft.
> -Brock
> DevelopMentor
> http://staff.develop.com/ballen
>
>> Adding that I have yet to come to understand the scope of the current
>> aspnetdb.mdb database schema and hope somebody who knows what the heck
>> all those columns actually mean and what they can be used for will
>> document it and doing it yesterday will not be soon enough for me.
>>
>> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
>> news:453106632490060869625168@.msnews.microsoft.com ...
>>
>>> Membership is purely for authentication. For extra user data you
>>> should look into the Profile.
>>>
>>> -Brock
>>> DevelopMentor
>>> http://staff.develop.com/ballen
>>>> the membership asp.net2.0I have many User attributes like telephone
>>>> number,
>>>> security ID, Country etc...
>>>> I must retrive these attributes after the user login.
>>>> How can I save do with the membership of asp.net2.0?
Its not a matter of like or dislike. I can't dislike something simply
because I do not understand it. Its after I come to understand something
that I can make a reasonable determination.

I'm confident the schema will be documented and many articles will appear --
eventually -- but again, yesterday would not have been too soon for me.

Where is Dino Esposito et. el. when you really need them? ;-)

--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/

"Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
news:460338632490389934897792@.msnews.microsoft.com ...
> Well, I'd agree. It'd be nice to have these documented, but on the other
> hand that's somewhat going against the idea of a provider (wether it be
> membership or profile). IOW, it's a black box of functionality. It's
> academically interesting to understand them, but too much info is a bad
> thing as one tends to want to modify things when you shouldn't. If you
> don't like their implementation, you can create your own Membership or
> Profile provider that works with all the UI controls just the same as the
> built in providers from Microsoft.
> -Brock
> DevelopMentor
> http://staff.develop.com/ballen
>
>> Adding that I have yet to come to understand the scope of the current
>> aspnetdb.mdb database schema and hope somebody who knows what the heck
>> all those columns actually mean and what they can be used for will
>> document it and doing it yesterday will not be soon enough for me.
>>
>> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
>> news:453106632490060869625168@.msnews.microsoft.com ...
>>
>>> Membership is purely for authentication. For extra user data you
>>> should look into the Profile.
>>>
>>> -Brock
>>> DevelopMentor
>>> http://staff.develop.com/ballen
>>>> the membership asp.net2.0I have many User attributes like telephone
>>>> number,
>>>> security ID, Country etc...
>>>> I must retrive these attributes after the user login.
>>>> How can I save do with the membership of asp.net2.0?
Try creating a new project and use the SQLProvider instedd of the
AccessProvider. If you do so then all the tables would be created and you
could visibly see the schema in the Visual Studio IDE.

"clintonG" wrote:

> Its not a matter of like or dislike. I can't dislike something simply
> because I do not understand it. Its after I come to understand something
> that I can make a reasonable determination.
> I'm confident the schema will be documented and many articles will appear --
> eventually -- but again, yesterday would not have been too soon for me.
> Where is Dino Esposito et. el. when you really need them? ;-)
> --
> <%= Clinton Gallagher
> METROmilwaukee "Regional Information Services"
> NET csgallagher AT metromilwaukee.com
> URL http://clintongallagher.metromilwaukee.com/
>
> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
> news:460338632490389934897792@.msnews.microsoft.com ...
> > Well, I'd agree. It'd be nice to have these documented, but on the other
> > hand that's somewhat going against the idea of a provider (wether it be
> > membership or profile). IOW, it's a black box of functionality. It's
> > academically interesting to understand them, but too much info is a bad
> > thing as one tends to want to modify things when you shouldn't. If you
> > don't like their implementation, you can create your own Membership or
> > Profile provider that works with all the UI controls just the same as the
> > built in providers from Microsoft.
> > -Brock
> > DevelopMentor
> > http://staff.develop.com/ballen
> >> Adding that I have yet to come to understand the scope of the current
> >> aspnetdb.mdb database schema and hope somebody who knows what the heck
> >> all those columns actually mean and what they can be used for will
> >> document it and doing it yesterday will not be soon enough for me.
> >>
> >> "Brock Allen" <ballen@.NOSPAMdevelop.com> wrote in message
> >> news:453106632490060869625168@.msnews.microsoft.com ...
> >>
> >>> Membership is purely for authentication. For extra user data you
> >>> should look into the Profile.
> >>>
> >>> -Brock
> >>> DevelopMentor
> >>> http://staff.develop.com/ballen
> >>>> the membership asp.net2.0I have many User attributes like telephone
> >>>> number,
> >>>> security ID, Country etc...
> >>>> I must retrive these attributes after the user login.
> >>>> How can I save do with the membership of asp.net2.0?
>