{"id":11,"date":"2008-04-27T15:04:00","date_gmt":"2008-04-27T19:04:00","guid":{"rendered":"http:\/\/everysport.net\/GamePlan3\/Default.aspx?tabid=489&EntryID=7"},"modified":"2009-06-17T09:36:52","modified_gmt":"2009-06-17T13:36:52","slug":"using-commerce-servers-upmmembershipprovider-with-dotnetnuke","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/2008\/04\/27\/using-commerce-servers-upmmembershipprovider-with-dotnetnuke\/","title":{"rendered":"Using Commerce Server’s UpmMembershipProvider with DotNetNuke"},"content":{"rendered":"

For those that are not familiar with the UpmMembershipProvider membership provider, it is a part of Microsoft’s Commerce Server 2007 product, and is the only provider that offers interoperability with Commerce Server.\u00a0 It replaces the older AuthManager functionality from Commerce Server 2002.\u00a0 More importantly, it provides an implementation of the System.Web.Membership.MembershipProvider class, and may thus be used in any ASP.NET application that utilizes the standard membership system.\u00a0 Read more about the UpmMembershipProvider in Microsoft’s MSDN documentation<\/span><\/a>.<\/p>\n

DotNetNuke<\/span><\/a> (DNN) is one such application that uses the ASP.NET membership system.\u00a0 Because I’ve been working so much with it lately, I decided to investigate whether these two strangers might be successfully introduced — and indeed they can.\u00a0 Google<\/span><\/a> tells me that I am the only person to date who has successfully accomplished this task (not that surprising, given its relatively esoteric nature).<\/p>\n

It turns out that this integration consists of three tasks: (1) configuring Commerce Server appropriately, (2) the routine tasks that one would expect in using the new provider, (3) and a small integration gotcha<\/span><\/a>.\u00a0\u00a0Herein I address these in order.<\/p>\n

Configuring Commerce Server<\/h2>\n

Commerce Server uses the GeneralInfo.email_address value of the UserObject profile object by default for authentication.\u00a0 This is great, except that DotNetNuke uses a generic login name during registration.\u00a0 While it’s possible to configure DNN to use e-mail addresses throughout its registration system, that’s a topic for a later date and beyond the scope of the task at hand.<\/p>\n

We are thus forced to move Commerce Server away from e-mail addresses in favor of a more generic login name.\u00a0 If you haven’t already configured your Commerce Server installation to use such a login name, you’ll need to do so.\u00a0 Amy describes this process in her newsgroup post here<\/span><\/a>.\u00a0 Thanks Amy!<\/p>\n

Web.Config Integration<\/h2>\n

Most developers will know that the first task in installing a new provider is updating the application’s web.config file with details about the provider.\u00a0 Accordingly, we add the following to our web.config:<\/p>\n

        <<\/span>membership<\/span> defaultProvider<\/span>=\"UpmMembershipProviderAdapter\"<\/span>\r\n                    userIsOnlineTimeWindow<\/span>=\"15\"<\/span>><\/span>\r\n            <<\/span>providers<\/span>><\/span>\r\n                <<\/span>clear<\/span>\/><\/span>\r\n                <<\/span>add<\/span> name<\/span>=\"UpmMembershipProviderAdapter\"<\/span>\r\n                     enablePasswordReset<\/span>=\"true\"<\/span>\r\n                     logonNameProperty<\/span>=\"GeneralInfo.login_name\"<\/span>\r\n                     enableCreateDate<\/span>=\"true\"<\/span>\r\n                     enableEmailAddress<\/span>=\"true\"<\/span>\r\n                     enableLastLoginDate<\/span>=\"true\"<\/span>\r\n                     profileDefinition<\/span>=\"UserObject\"<\/span>\r\n                     requiresApproval<\/span>=\"true\"<\/span>\r\n                     minRequiredPasswordLength<\/span>=\"5\"<\/span>\r\n                     minRequiredNonalphanumericCharacters<\/span>=\"0\"<\/span>\r\n                     maxInvalidPasswordAttempts<\/span>=\"5\"<\/span>\r\n                     passwordAttemptWindows<\/span>=\"15\"<\/span>\r\n                     passwordLockoutPeriod<\/span>=\"10\"<\/span>\r\n                    type<\/span>=\"BrandonHaynes.Membership.UpmMembershipProviderAdapter<\/strong>\"<\/span>\/><\/span>\r\n            <\/<\/span>providers<\/span>><\/span>\r\n        <\/<\/span>membership<\/span>><\/span><\/pre>\n
Two comments about this entry:<\/p>\n
    \n
  1. Most attributes are straightforward and default here, including: enablePasswordReset, loginNameProperty, enableCreateDate, enableEmailAddress, enableLastLoginDate, profileDefinition.\u00a0 Note that the UpmMembershipProvider does not support many of the attributes available in the AspNetSqlMembershipProvider; see the MSDN documentation<\/span><\/a> for more details.\u00a0 This can be a source of frustration, as the provider does not complain when an unsupported attribute is supplied.<\/li>\n
  2. I did not directly use the UpmMembershipProvider class located in the Microsoft.CommerceServer.Runtime assembly.\u00a0 The reason for this is discussed below as a gotcha<\/span><\/a>.<\/li>\n<\/ol>\n
    Additionally, you’ll need to copy over all the required Commerce Server files to your DNN installation.\u00a0 These can come from the StarterSite or CSharpSite (obviously this choice will impact your mappings, and any production application will likely have customized these files).\u00a0 These files include:<\/p>\n
    \n