Architecture :: Single Sign On Web And Windows Apps?
Sep 18, 2010
We, at our company, are developing a file sharing application which will allow users to upload/download files. This application will be part of the suite of other applications. We will be adding a desktop client (windows app) which is an upload/download manager which will assist users to queue in multiple large files for upload/download. There are a couple of questions related to design for these applications:
1. We would like to implement Single Sign-On for all these applications (including desktop client). We would like users to login to web and once they do that, they can browse through applications without logging in again. We will be implementing a authetication service using WCF. The requirement is that we do not want to add authentication functionality to desktop client. So users will need to login to our web application. We can write cookie to user's machines and will work for web applications. Can the desktop client use the same cookie to autheticate itself? Or there are other ways we can achieve it? 2. We also do not want that when desktop client is uploading/downloading multiple files that its session is expired and the user need to re-authenticate through web. How can we achieve it? How does other Upload/Download Managers (like MS File Trasnfer Manager) work?
-I've to centralize users' passwords in my domain and have visibility of them.
-Each user must change his own password each 3 months.
-Each user must have only one password for the access to Windows,Intranet application and ERP application
Is there a way to block all user accounts periodically and asking them to insert the new password after the logon to windows?after that i could make a query that update the passwrod in Intranet and ERP application.
I'm starting to plan an architecture for a big web application, and I wanted to get suggestions and/or recommendations on where to begin and which technologies and/or frameworks to use.The application will be an Intranet-based web site using Windows authentication, running on IIS and using SQL Server and ASP.NET. It'll need to be structured as a main/shell application with sub-applications that are "pluggable" based on some configuration settings.
I'm starting to think about and develop an architecture for a big web application, and I wanted to get suggestions and/or recommendations on which technologies and/or frameworks to use.The application will be an Intranet-based web site using Windows authentication, running on IIS and using ASP.NET. It'll need to be structured as a main web application with sub-web applications. Essentially, the entire scope is a composite browser-based,Intranet application that is composed of discrete, functionally complete modules or sub-applications.
i'm facing a problem with transfering data between two web applicatins on two different servers. For example on page A
I have a login box with LoginName textbox and Password textbox and Login button. What I am trying to achieve is that when i press Login button I will transfer data from Login and Password textboxes to page B and .net code on page B will try to validate the logging user. I was trying code like this but it won't works on page A
[Code]....
and on page B in Page_Load event
[Code]....
I was thinking of using Web Service between these apps, however i am not certain that it will works.
I'm starting to plan an architecture for a big web application, and I wanted to get suggestions and/or recommendations on where to begin and which technologies and/or frameworks to use. The application will be an Intranet-based web site using Windows authentication, running on IIS and using SQL Server and ASP.NET. It'll need to be structured as a main/shell application with sub-applications that are "pluggable" based on some configuration settings.
The main or shell application is to provide the overall user interface structure - header/footer, dynamically built tabs for each available sub-app, and a content area in which the sub-application will be loaded when the user clicks on the sub-application's tab. So, on start-up of the main/shell application, configuration information will be queried from a database, and, based on the user and which of the sub-apps are available, the main or shell app would dynamically build tabs (or buttons or something) as a way to access each individual application. On start-up, the content area will be populated with the "home" sub-app. But, clicking on an sub-app tab will cause the content area to be populated with the sub-app corresponding to the tab.
For example, we're going to have a reports application, a display application, and probably a couple other distinct applications. On startup of the main/shell application, after determining who the user is, the main app will query the database to determine which sub-apps the user can use and build out the UI. Then the user can navigate between available sub-apps and do their work in each. Finally, the entire app and all sub-apps need to be a layered design with presentation, service, business, and data access layers, as well as cross-cutting objects for things such as logging, exception handling, etc.
Anyway, my questions revolve around where to begin to plan something like this application. What technologies/frameworks would work best in developing a solution for this application? MVC? MVP? WCSF? EF? NHibernate? Enterprise Library? Repository Pattern? Others? I know all these technologies/frameworks are not used for the same purpose, but knowing which ones to focus on is a little overwhelming. Which ones would be the best choice(s) for a solution? Which ones work well together for an end-to-end design? How would one structure the VS project for something like this?
I maintain a college website. I also create various small web apps for the college (staff directory, online credit schedules, etc.). Currently, I have been using VS2010 and clicked on File - New Web Site - ASP.NET Empty Web Site for the main college website and File - New Web Site - ASP.NET Dynamic Data Entities Web Site for each of my apps.
Each is in its own separate directory in my development environment. The main site is "published" via VS2010's Copy Web Site tool in the Solution Explorer. The individual web apps are copied into unique physical directories on the Web server, and then via IIS7 Manager, a virtual directory is created on the college's web site for each app.
I have now run into a situation where I would like to create a new web app that utilizes some of the images and master pages from the college's web site. How do I create a New Web Site in VS2010 that can see/recognize/access the files from another web site? Namely, the college's main web site.
I have basic Single Sign-On working across 2 MVC sites (call them SiteA and SiteB) using something along the lines of the following method:http://forums.asp.net/p/1023838/2614630.aspxThey are on sub-domains of the same domain and share hashencryption keys etc in web.config. I've modified the cookie so it is accessible to all Sites on the same domain. All of this seems to be working ok.The sites are on separate servers without access to the same SQL database, so only SiteA actually holds the user login details. SiteB has a membership database, but with empty users.This works fine for my required scenario which is:1) User logs into SiteA2) The application loads data from SiteA (by AJAX) and SiteB (by AJAX using JSONP)I have the following LogOn Action on my AccountController for SiteA, which is where the "magic" happens:
[HttpPost] public ActionResult LogOn(LogOnModel model, string returnUrl) {
i just want to confirm if what am trying to do is a good deployment practice. i have two applications am deploying. A web application using web setup project and a windows application using setup project. Due to some constraints, am merging the two deployments and so i intend installing the windows application in the intepub folder (same location as where the *.aspx will reside). Is this crazy? the windows application has a windows service
we have developed a ASP.NET application that required a username and password to login and use the application.Now on of our customers wants to use Single Sign on with their Microsoft Sharepoint Portal.
Basically they want their users to be able to login to the portal, and then be able to access our application, without having to provide their login details again.Does anyone have experience with implementing Single Sign on?
I have a web app located at [URL] and I have several domains, such as [URL], [URL], etc. all pointing to the same directory in IIS. I use Host Headers to acheive this by setting the 'Host Header Values' under properties for the main site (under the Web site identification section). Based on the host header value I perform different functions in my pages.
Because of the way I have it set up, all the domains share the same files, web.config, etc. I have set the 'machinekey' in my web.config and have forms authemtication. However, when I go to MyMainSite.com and log in and then the user clicks a link and gets directed to MyFirstSite.com the user is shown as logged out. I need the user to be logged in and I need to be able to access the logged in user profile to display certain information. I thought by setting the 'machinekey', i could acheive this, but it does not seem to work.
how to go about having a single log on for my users?
The articles I have found show the same domain or have different domains each with a different web.config. The way they describe does not seem to work for me.
m using visual studio 2008.my requirement is to implement single sign on across many domains without using cookies. is this possible?for example, i have 3 domains (hosted in 3 different systems).[URL]i implemented single sign on with cookies, if the sites are hosted in single system then it is working. but it doesnt work if cookies are disabled.i tried all made all possible google searches, but couldnt find anything useful.
I need to create a single sign-on structure and my question is: is SSL a must?
Details: The application will have a link to my web application. When the user clicks that link, their local username will be passed to my web app at which point a look-up in a mapping file is done. If that local username exists in the map, then the user is logged in. If not, then the user will be prompted to enter their network username and password, and when authenticated, an entry in the map will be created.
How do I ensure that user is who they say they are and not Joe Blow from off the street sending in an HTTP POST request with that username?
Do I have to use SSL (and if so, what does that entail)? Would adding a salt and encrypting the username be sufficient? Maybe locking it down so the source IP has to be within a controlled range?
My web app runs on IIS 6/7 and uses the ASP.NET MVC framework, if that is important.
It will not give me a response back other than "Nothing"
I am new to web services and single sign-on, and any help would be greatly appreciated. I am using the standard log-in system for vs, and want it so that after they log in, and load my special page, it redirects them to the kickapps app, where they are already signed in.
I've only worked with web services a little bit. I am working on a project now using another developer's code as a template. It is code for a single sign on (SSO).
Also let me say, I have been coding in VB6/VB.NET for the past six years and am learning C# (that is what the other developer's code is written in).
setAppCredentials() is the beginning of a lot of sub-calls and I have gotten that all to work when I was running the service from within its own Visual Studio project.
Where I am having the problem is setting credentialHeader.Username and credentialHeader.Password. credentialHeader is nothing when I call validateCredentials().
I didn't see how I had these exposed to me in order to set them. So the developer said Create a client that consumes that service and set the values there and call your method.. But I still don't see how it's exposed to my consumer. I have this line of code in the consumer
Code : Dim myWebService As New localhost.xxxMemberService
(Back to VB!,) but I still don't see credentialHeader exposed.
The only other thing I see in the webservice code that might be relevant is this:
I have this tutorial on Single Sign On with forms authentication.The following link:
[URL]
I did item number 1 which is "SSO for parent and child application in the virtual sub-directory" and it works fine BUT I can't seem to stay logged in because each time I leave and reenter the application I get redirected to the login page.
Is this an inherent feature of forms authentication?
What happened to authorized cookie generated by forms authentication?
While waiting for responses, I will look for answers.
I have a Single Sign-on solution which is working great in our test environment. It uses Cross-Sub-Domain cookies to share the authentication ticket between 2 web applications. Sign-on is done only on one of the applications and on the second site the user is authenticated by the cookie created by the first site.The problem is that when I roll it into the production environment the single sign-on no longer works. I'm looking for any ideas on why this might be. More details below:1) Both apps are implemented using ASP.NET MVC2
We have intranet based web application in ASP.Net, needs to be configure for single sign on authentication at client place.
Our client has existing intranet based web site in classic ASP. After successful login to this site in asp, employee will have a link to access our web portal without entering any credentials again. Please note that both sites are having differnet virtual directories or different domains.
Is there any way to achieve this sinlge sign on authentication than LDAP or Cokie based authentication.
Does Microsoft 3.5 provides some enterprise service to acheive the same?
How can I use a Guid for implementing single sign on the same domain? I can't use sessions as the different web apps would open in new windows hence loosing the session.
Technology used: ASP.net 3.5, MVC2 architecture, C#.
I have a parent web application and a child web application. I am using single sign on between them. The child application is supposed to redirect anonymous users to the login page of the parent application We just updated both to .net 4.0 framework and now the SSO doesn't work anymore.The setup is as follows. I have the machineKey tag all set up with validation key and decryption key in both applications.then, for authentication tag i have the following in the child app (I have replaced the actual parent app's url with "parentApp" for privacy):
I am trying to use the concept of Single Sign On (SSO) in my asp.net application.
for the purpose i have created a main domain say mydomain.com.
now i have 2 subdomains sub1.mydomain.com & sub2.mydomain.com.
I am running these very fine. But now I want to have a SSO for my domains. For the same have
googled lot and found some stuff such as adding machine key to web.config and specifying domain names in cookies.
But it is not at all working for me. when I specify the domain name for cookies i am unable to sign out.
I am using FormsAuthentication in asp.net.
Following is the code I have in my web.config.
[Code]....
I have the same code in web.config of each domain. I have placed the code for each domain in different directory on my website. for ex. mydomain.com ---------> F:/HostedSites/mydomain sub1.mydomain.com ---------> F:/HostedSites/subdomain1 sub2.mydomain.com ---------> F:/HostedSites/subdomain2
my Authentication code is
[Code].... and sign out code is
[Code]....
Can anybody tell me where exactly I am wrong ? what changes do i need to do at server end also.
I am checking this on my testing domain ie. mydomain.tv. can this be a problem ?
