I'm having some trouble getting YAF (I'm using version 1.9.1.8 at the moment) working properly with an existing ASP.NET website. This centers around integration issues, but unlike most of the users in the threads I have found here, I do not want to integrate my existing Membership users with YAF users, nor the other way around. And in fact, my existing users cannot access the forums, as one would expect.

However, a YAF user can access my existing site as a logged-in user, which I don't understand and would like to prevent. I don't understand it because the user does not exist in the ASP.NET membership tables. I assume what is happening is that since I am just checking authentication in most places, rather than specific membership or roles, it is treating YAF user authentication just as it would ASP.NET user authentication (and my login control, in login template, shows the YAF userID, boardID, and username when logged in this way). While I assume I could address this by checking specific role-group membership instead of just authentication, that would most likely just confuse the user since they would see themselves as logged in with a strange username, and be forced to log out and back in again with their ASP.NET membership credentials.

How can I completely separate the YAF authentication from my existing ASP.NET authentication setup? I would like to keep all the tables in the same database, but separate the users and authentication status completely. Is this possible? Any input appreciated! I'm still just testing, so I can try a different version if that is recommended.

Thanks,

Scott

Thanks for the reply. My production site is hosted on GoDaddy so the solution is a non-starter if it in fact relies on creating a separate IIS application... I don't have such discrete control over the web server as that. However, the Auth settings tutorial you linked to mentions that a separate web.config file in a sub-directory can override the main site settings. I imagine this is true for some things and not others, since I noticed that YAF requires a number of modifications in the root web.config, but would the forums still work if I overrode the parent site configuration with a web.config file in the YAF sub-directory? Or would that break other things?

That's why I was surprised that I was running into problems with it... I didn't think there could be any conflicts without those features in the older version.

I'll give the web.config changes in a sub-directory a try and post back my results in case anyone else ever runs into the issue.

Thanks again!