Access Authentication

[Shaker]

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.dotnet.framework.aspnet.security (More info?)

Hi,
I have an ASP.Net Application,
This application is accessed based on user identiy authorization.
This application is hosed on server locted on NT domain (based On AD) groups.

This application is also accessed from another workgroup (not defined on
main NT domain).

I could control the access per user when using
<authentication mode="Windows"/>

and
<authorization>
<allow users="......./>

But this will Deny the other workgroup from seeing the application.

How could I provide the access per user level for two differnt domains.

Note:
The IIS security settings is: Anonmous Access and Integrated Windows Auth.


Help


--
MCSD not .Net yet

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.dotnet.framework.aspnet.security (More info?)

You can use Forms based authentication and write your own authentication
inheriting from the authentication base class.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"Shaker" <Shaker@discussions.microsoft.com> wrote in message
news:8DD0A14E-C0BD-4430-803F-19F49C9D1FFA@microsoft.com...
> Hi,
> I have an ASP.Net Application,
> This application is accessed based on user identiy authorization.
> This application is hosed on server locted on NT domain (based On AD)
groups.
>
> This application is also accessed from another workgroup (not defined on
> main NT domain).
>
> I could control the access per user when using
> <authentication mode="Windows"/>
>
> and
> <authorization>
> <allow users="......./>
>
> But this will Deny the other workgroup from seeing the application.
>
> How could I provide the access per user level for two differnt domains.
>
> Note:
> The IIS security settings is: Anonmous Access and Integrated Windows Auth.
>
>
> Help
>
>
> --
> MCSD not .Net yet

 

[Shaker]

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.dotnet.framework.aspnet.security (More info?)

But I still need to base my authentication based on Windows, without needing
to do further authentication Forms.

"Ryan Hanisco" wrote:

> You can use Forms based authentication and write your own authentication
> inheriting from the authentication base class.
>
> --
> Ryan Hanisco
> MCSE, MCDBA
> Flagship Integration Services
>
> "Shaker" <Shaker@discussions.microsoft.com> wrote in message
> news:8DD0A14E-C0BD-4430-803F-19F49C9D1FFA@microsoft.com...
> > Hi,
> > I have an ASP.Net Application,
> > This application is accessed based on user identiy authorization.
> > This application is hosed on server locted on NT domain (based On AD)
> groups.
> >
> > This application is also accessed from another workgroup (not defined on
> > main NT domain).
> >
> > I could control the access per user when using
> > <authentication mode="Windows"/>
> >
> > and
> > <authorization>
> > <allow users="......./>
> >
> > But this will Deny the other workgroup from seeing the application.
> >
> > How could I provide the access per user level for two differnt domains.
> >
> > Note:
> > The IIS security settings is: Anonmous Access and Integrated Windows Auth.
> >
> >
> > Help
> >
> >
> > --
> > MCSD not .Net yet
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.dotnet.framework.aspnet.security (More info?)

You can tie the form to AD easily... that is a behaviour of the form...

Otherwise, you'll need to inherit the security authentication and roll your
own.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"Shaker" <Shaker@discussions.microsoft.com> wrote in message
news:AEB06382-6B48-4CC7-BB23-ACBC523E1595@microsoft.com...
> But I still need to base my authentication based on Windows, without
needing
> to do further authentication Forms.
>
> "Ryan Hanisco" wrote:
>
> > You can use Forms based authentication and write your own authentication
> > inheriting from the authentication base class.
> >
> > --
> > Ryan Hanisco
> > MCSE, MCDBA
> > Flagship Integration Services
> >
> > "Shaker" <Shaker@discussions.microsoft.com> wrote in message
> > news:8DD0A14E-C0BD-4430-803F-19F49C9D1FFA@microsoft.com...
> > > Hi,
> > > I have an ASP.Net Application,
> > > This application is accessed based on user identiy authorization.
> > > This application is hosed on server locted on NT domain (based On AD)
> > groups.
> > >
> > > This application is also accessed from another workgroup (not defined
on
> > > main NT domain).
> > >
> > > I could control the access per user when using
> > > <authentication mode="Windows"/>
> > >
> > > and
> > > <authorization>
> > > <allow users="......./>
> > >
> > > But this will Deny the other workgroup from seeing the application.
> > >
> > > How could I provide the access per user level for two differnt
domains.
> > >
> > > Note:
> > > The IIS security settings is: Anonmous Access and Integrated Windows
Auth.
> > >
> > >
> > > Help
> > >
> > >
> > > --
> > > MCSD not .Net yet
> >
> >
> >

 

[Shaker]

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.dotnet.framework.aspnet.security (More info?)

Can you explain more details of how to do, or refere where it is?

Provided that I don't want to ask the user for more Passwords and ID more
than the time he did once he logged to the network, either to NT Domain(AD)
or to Workgroup domain (Not AD).

"Ryan Hanisco" wrote:

> You can tie the form to AD easily... that is a behaviour of the form...
>
> Otherwise, you'll need to inherit the security authentication and roll your
> own.
>
> --
> Ryan Hanisco
> MCSE, MCDBA
> Flagship Integration Services
>
> "Shaker" <Shaker@discussions.microsoft.com> wrote in message
> news:AEB06382-6B48-4CC7-BB23-ACBC523E1595@microsoft.com...
> > But I still need to base my authentication based on Windows, without
> needing
> > to do further authentication Forms.
> >
> > "Ryan Hanisco" wrote:
> >
> > > You can use Forms based authentication and write your own authentication
> > > inheriting from the authentication base class.
> > >
> > > --
> > > Ryan Hanisco
> > > MCSE, MCDBA
> > > Flagship Integration Services
> > >
> > > "Shaker" <Shaker@discussions.microsoft.com> wrote in message
> > > news:8DD0A14E-C0BD-4430-803F-19F49C9D1FFA@microsoft.com...
> > > > Hi,
> > > > I have an ASP.Net Application,
> > > > This application is accessed based on user identiy authorization.
> > > > This application is hosed on server locted on NT domain (based On AD)
> > > groups.
> > > >
> > > > This application is also accessed from another workgroup (not defined
> on
> > > > main NT domain).
> > > >
> > > > I could control the access per user when using
> > > > <authentication mode="Windows"/>
> > > >
> > > > and
> > > > <authorization>
> > > > <allow users="......./>
> > > >
> > > > But this will Deny the other workgroup from seeing the application.
> > > >
> > > > How could I provide the access per user level for two differnt
> domains.
> > > >
> > > > Note:
> > > > The IIS security settings is: Anonmous Access and Integrated Windows
> Auth.
> > > >
> > > >
> > > > Help
> > > >
> > > >
> > > > --
> > > > MCSD not .Net yet
> > >
> > >
> > >
>
>
>