Hi ,
I'm using FormsAuthentication as authentication mechanism and configured to use SqlServerMembershipProvider. I'm using community sp1.
I have stripped out everything else on the login button apart from the authentication for debug purposes and I'm still getting the following exception when I try to login:
"The type 'EPiServer.Community.ImageGallery.ImageGallery' does not have an attribute with the name 'Owner' assigned to it."
The user exists on the current membership database but it does not get "created" in the community tables.
Thanks.

Otavio Soccol

Has anyone had a chance to look into this, it is getting critical for us.

Thanks.

Hi Otavio,

It seems like you are using code from the Relate+ package, but maybe not a Relate+ default database?! In the default Relate+ setup there is a custom attribute named "Owner" on the ImageGallery object.

You can check your custom attributes by login into to edit mode -> Community tabb -> Attributes -> choose ImageGallery in the dropdown. If there is no attribute named Owner, you can add it - it should be of type EPiServer.Common.Security.IUser (see documentation if you need information how to do this). Alternatively you can alter the code on the site.

Best regards,
Tom Stenius

Many thanks Tom, it is working now.

Have a great day. 

Hi! I think Im having the same problem as above. The user exists on the current membership database (Windows) but it does not get "created" in the community tables. This is from web.config

  <roleManager enabled="true" defaultProvider="WindowsRoleProvider" cacheRolesInCookie="true">
   <providers>
    <clear/>
    <add name="WindowsRoleProvider" applicationName="EPiServerSample" type="EPiServer.Security.WindowsRoleProvider, EPiServer"/>
   </providers>
  </roleManager>
  <membership defaultProvider="EPiServerCommonIntegrationMembershipProvider" userIsOnlineTimeWindow="10">
   <providers>
    <clear/>
    <add name="WindowsMembershipProvider" type="EPiServer.Security.WindowsMembershipProvider, EPiServer" deletePrefix="BUILTIN\" searchByEmail="true"/>
    <add name="EPiServerCommonIntegrationMembershipProvider" applicationName="EPiServerCommonApplication" type="EPiServer.Common.Web.Authorization.IntegrationMembershipProvider, EPiServer.Common.Web.Authorization" provider="WindowsMembershipProvider" roleToSynchronize1="Everyone"/>
   </providers>
  </membership>

 

We are using integrated windows authentication (not anonymous acces). Any ideas?

Hi Erik,

I did not have to use the WindowsMembershipProvider but I assuming it works in a similar way on matters of EpiServer membership integration but double check Tom's post. 

What solved my problem was to set the custom attribute named "Owner" on the ImageGallery object as suggested by Tom and that is due to the fact we have used code from the Relate+ package and not a Relate+ default database.

I would maybe suggest to change the roleToSynchronize1="Everyone" to roleToSynchronize1="*" but I am not sure if it will make any difference.

Hope that helps somehow and good luck.

 

Otavio Soccol

Hi,

In the Windows Authentication setup you have to approch it a bit differently. See my new blog post here.

Best regards,
Tom

Excellent post, that did the trick! :) Thanks

(Remember to remove the preCondition="managedHandler" attribute if you're not using IIS7)

Nice!

I will add your note to my blog post as well.

 //Tom 

Hi! I got one more question in this matter. I'm noticing that we are losing the community members e-mail addresses. We are storing them in the EMail property on IUser. Apparently, when logging in the e-mail address of the logged in user gets overwritten with string.Empty. Is there a way of avoiding this, or should we create a new e-mail attribute on the users instead?
Thanks!
Erik Lidälv

Hi Erik,

I'm sorry to say that I don't beleive you can change this behavior. Either you do as you propose, i.e. create a new user attribute. Or you reverse engineer the HTTP module and make your own with custom behavior.

Best regards,

Tom 

 

Each time a user logs in the IntegrationMembershipProvider calls the SynchronizeUser Method of the Integrator class in EPiServer.Common.Web.Authorization namespace. If the Email property is empty for the user in the underlying MembershipProvider it gets copied to the CommonUser-table overwriting any information registered there. One solution is to write the email address of the user back to the underlying MembershipProvider.

/MHo