Search results matching tag 'membership'

Membership Provider Misc. Settings in WMI

Switche — Wed, 12 Mar 2008 15:57:18 GMT

I am trying to manage custom membership providers via WMI's WebAdministration provider. I can add, remove, and modify membership providers, but I cannot set any properties on providers other than the "Name" and "Type" properties. For example, I need to manage the "ConnectionString" and "ApplicationName" properties. These properties are set in the web.config file for this path, and function properly, but the properties do not exist in the provider object I am working with in WMI.

The objects I am working with are MembershipSection (ConfigurationSection object), its MembershipSection.Providers property (ProvidersSettings object) and then that object's Providers property (array of NameTypeElement objects). WMI Object Browser confirms that even existing providers with the "ApplicationName" and "ConnectionString" properties do not exhibit any properties except Name and Type in WMI. The NameTypeElement object's class definition does not contain any other properties than these two (see http://msdn2.microsoft.com/en-us/library/aa347551(VS.85).aspx).

All of this makes me believe I'm either looking at the incorrect object, or that WMI cannot manage these properties. I know how to use appcmd or ASP.NET to set these properties, but would like to know how to do so in WMI.

Thanks

Re: Getting the XML Membership Provider to work with Forms Authentication

mvolo — Wed, 23 Jan 2008 17:35:59 GMT

Hi Drichfield,

Unfortunately a recent security change now prevents the ability to manage users and roles from IIS Manager using providers provided as part of your application (think /App_Code or /BIN).

To work around this, you can compile the provider into a strongly-named signed assembly, and register it in the GAC. Then, use the full assembly-qualified type in the provider's configuration to identify this provider. This will allow you to use IIS Manager, which is by far the easiest way to create and manage Membership users.

Without IIS Manager, you can still create and manage users using Membership APIs directly even if you use application-based providers, but that requires you to write a custom page to manage the users or roles. You can use the CreateUserWizard control to quickly do this in an ASP.NET page: http://msdn2.microsoft.com/en-us/library/ms178334.aspx.

As far as your "Could not load type error", can you show the contents of your web.config file, particularly the <membership> configuration section?

Thanks,

Mike Volodarsky

Program Manager
IIS Core Server
Visit mvolo.com for more IIS 7.0 posts, tools, and info

VS 2005 web app Login control problem. I can login using http://localhost/appname but not using http://computername/appname/

packerfan — Fri, 17 Aug 2007 15:35:42 GMT

My problem is getting the login control in a Visual Studio 2005 web application funtionality to work when using the computer name rather than localhost. If I put in a wrong password I get an error message "Your login attempt was not successful" so it is checking the database correctly but if I put in the right password it seems to reload the login page instead of forwarding to the default page. As I said this doesn't happen if I use localhost . If I run this same app on an XP pro IIS6 box I don't have any problems. Thanks for any help to track down this issue.