G
Guest
I’m working on the architecture of a distributed (multi-tier) application,
which is going to be created using Microsoft .NET technologies. I’d like my
Presentation layer (ASP.NET Web Application) communicate with the Business
layer through a Service Interface component (ASP.NET Web Service or a WCF
Service). The Service Interface is expected to be accessed not only
internally by the Presentation layer but also by external systems (it plays
the roles of both internal and external interfaces).
I’m going to use ASP.NET 2.0 Membership for authentication in the
Presentation layer and to use it also in the Service Interface component for
authenticating the calls coming from external systems. In this scenario, when
the Presentation layer component (ASP.NET application) calls the Service
Interface component, is it possible somehow to pass a sort of a token or
authentication ticket from the Presentation layer to the Service Interface
component in order to avoid additional authentication of a user at the
Service Interface layer, since the user was already successfully
authenticated at the Presentation layer?
What are the possible solutions, in general, if I want to make a Service
Interface component authenticate calls coming from external systems, but not
the calls coming from the Presentation layer (in this case I need the user
identity to be passed to the Service Interface from the Presentation layer
without additional authentication)?
Any suggestions and opinions are welcome. Thank you.
which is going to be created using Microsoft .NET technologies. I’d like my
Presentation layer (ASP.NET Web Application) communicate with the Business
layer through a Service Interface component (ASP.NET Web Service or a WCF
Service). The Service Interface is expected to be accessed not only
internally by the Presentation layer but also by external systems (it plays
the roles of both internal and external interfaces).
I’m going to use ASP.NET 2.0 Membership for authentication in the
Presentation layer and to use it also in the Service Interface component for
authenticating the calls coming from external systems. In this scenario, when
the Presentation layer component (ASP.NET application) calls the Service
Interface component, is it possible somehow to pass a sort of a token or
authentication ticket from the Presentation layer to the Service Interface
component in order to avoid additional authentication of a user at the
Service Interface layer, since the user was already successfully
authenticated at the Presentation layer?
What are the possible solutions, in general, if I want to make a Service
Interface component authenticate calls coming from external systems, but not
the calls coming from the Presentation layer (in this case I need the user
identity to be passed to the Service Interface from the Presentation layer
without additional authentication)?
Any suggestions and opinions are welcome. Thank you.