ida:Domain un-used setting? - c#

When creating an authenticated C# MVC Project it creates an app setting called ida:Domain
However this is never used anywhere in the code generated and as we're using Open ID I cannot see any benefit to having it in the config.
Please can someone tell me if it is used under the covers by any IIS or Microsoft library and what for?

I found this question unanswered. Although it is late, but still no harm doing that.
These configurations are used by ASP.NET MVC Identity service to manage IDentity and Access (IDA) for Azure Active Directory users.
Hope that helps.

Related

Publishing ASP.NET application using third party hosting

I have developed an ASP.NET C# Web application with 2 web forms and I have purchased a domain from Fasthosts in order to host my site. I have changed the server to be Windows-based and used the correct ftp details to upload my app to the site. The only problem I am having is that when the site is published I am receiving this error.
I am hoping that this issue is fairly easy to resolve. Any help on what I can do to get around this issue would be much appreciated. Thanks:)
Since you have not provided details of any set up using IIS, I would imagine that your issue is that you have simply deployed the file and gone to the URL expecting the site to be there. Normally you'd have some setup to do, unless they are handling that for you?
Have you make sure that you have setup your default page? Do they support .net core? Maybe this post https://windowswebhostingreview.com/troubleshoot-403-error-when-publishing-asp-net-core/ can help you.

Using ASP.NET Application Account Login for Hosted Websites

Visual Studio 2010 has a way to create a new website.
I have done that with 4 different websites, all are hosted remotely on Godaddy, and they all run fine.
All of these sites come with a default Microsoft login link:
The link goes to documentation on MSDN, but that documentation covers everything in depth. I'm not a DBA, and I have never figured out how to get one of my websites to use this feature.
In the past, I have either deleted those links or set them so they were not displayed.
Now, I'd like to learn what is required to getting them to working - just something basic.
I went there and created a new, blank Microsoft SQL database. The tables are not setup, though. That may be all I need!
Looking at the default settings in the web.config file, it looks like I can simply edit the connection string to be what I need.
Microsoft posts a link in their code, but I must confess that I really don't know what I'm looking for, so it is hard to tell when I am looking at the solution.
For a hosted website (like GoDaddy), does anyone know how to get the database setup?
I'm looking for a spoon fed, Step-By-Step, "How To" for dummies like me that spend most of their time developing Windows Forms.
You are using ASP.Net - Legacy SQL Membership Provider. It has been deprecated long time ago.
ASP.Net Identity 2 is new, but it requires .Net 4.5
Closest to Legacy Membership Provider is ASP.NET Universal Providers.
Link from the 2nd picture is for web.config in general. It doesn't include any information about Membership Provider.

ASP.NET WebSecurity object shared between projects?

First of all, I'm not familiar with Web development so I might be missing something basic here. Do excuse me if that's really the case.
I'm currently working on a web application (not created by me), which is based on another web app.
Both applications share similar user log in code, but user account info are stored in different databases.
However, after logging in to 1 of the app, the WebSecurity.IsAuthenticated flag is also true on the other app (detected as logged on). Is this behaviour expected?
In case this information is of any use..
1 of the app uses ASP.NET development server while the other uses ISS express.
This is not exactly an answer to my initial question.
That has been answered by #Esa in the comment above --> Setting machine key to Web.Config.
The following is an answer to the problem I mentioned in the comment.
(Should I have posted this in comment instead?)
Both applications were overwriting the same __RequestVerificationToken cookie, which caused error "The anti-forgery token could not be decrypted..." when navigating.
This is because both applications were at the same path of "localhost:xxxxx" and hence detected as the same site. The error can be avoided by changing the virtual path of either application.
For VS, Project properties -> Web (tab) -> Virtual path

Can we use Authentication in 'Forms' and as well in 'Windows' for a .net web application

We have an application in Access for UI and MS Sql server as Database server. We now decided to build a new application in web application for UI. This web application is only used by the employees who work for the company. But later we decided to host this web application on outside server. So the user (from this company only.) can able to login anywhere in the world. First I thought creating the web application using 'windows' authentication thinking we may be using it as an intranet web application. But now my manager asked me to use both 'Forms' and as well as 'Windows' for using this application and this web application will be hosted on outside server. I really don't catch his point of using both types of authentication.
Please help me is there any ways to use both authentication methods and please also suggest me why we might need to use both authentication methods. If so could you please help me with some instructions of using the both authentication types. Thank you so much for taking time to read and understand my question and helping me in this regard.
#Will explained in his comment as to why both forms of authentication is preferred. The following article shows one way to implement what you need.
You may also want to check the following article to better understand how Windows Authentication works.

Implementing DotNetOpenid in my asp.net website

I am trying to implement DotNetOpenid in my asp.net website. However, the more I try to read up on DotNetOpenid, the more confused I get. My initial goal is to allow user login process (similar to StackOverflow).
I attempted to get some help via this question dotnetopenid tutorial
but was unsuccessful (since I am not using MVC)
How can I get a tutorial that would help me accomplish that?
I would first start at the developers site
Coding Guidelines
Quick Start
Code Snippets
I have been posting my questions here Support Forum. Pretty helpful.
The ASP.NET OpenID web site (C#) project template isn't a tuturial, but it does create a functioning OpenID ASP.NET web site.
I just installed it and was able to get a site up and running. Here are a few gotchas that I ran into:
When you create a new project using the template, do not choose a deep path - this will create problems during database creation.
When you first run the application, you'll hit an exception - don't worry about it. When you get the YSOD, simply browse to the Setup.aspx page mentioned in the instructions.
If you don't have an OpenID, you'll need to get one. The initial page loaded after database creation has a 'Get OpenID' link if you need to get one. It's a simple process and only takes a few minutes.
Once you get through that, you'll have a working implementation of an OpenID web site.
You might also want to check out the DotNet OpenAuth ASP.NET Controls.
HTH
Edit
For anyone interested, there is also an ASP.NET MVC 2 OpenID web site (C#) template. I'm surprised #Andrew Arnott answered the other question and didn't mention these, since he is the author.

Categories

Resources