21 Oct 2011
28 Oct 2011
Link to this post
I am working on a proof of concept to see if Sitefinity will work for a client. In particular, I am trying to show that there is a way to handle multiple categories of members. I currently have 3 Membership Providers:
1. The default membership provider.
2. A new member provider that uses Telerik.Sitefinity.Security.Data.OpenAccessMembershipProvider and has applicationName = "Backend/". This is called AgentMember. Iset this up using Advanced Settings. The purpose of this is to show a segregated category of members with different profiles than the default membership provider. I also added a custom profile that was applied only to this membership provider.
3. The LDAP provider. This was setup through Advanced Settings.
Here are the issues that I have run into:
1. Users created under the default membership provider and under the AgentMember provider are both shown under both categories in the Users page. The users are listed twice when the "All Providers" filter is chosen.
2. The custom profile appears for both LDAP members and AgentMembers when a user is edited.
3. When an AgentMember edits their profile the custom profile does not appear.
4. I cannot login as an LDAP user. I always get invalid username password combination. Is Sitefinity supposed to automatically login the user if they are logged into the domain or does the user have to explicitly login to Sitefinity?
5. When I edit an LDAP user account I cannot save the changes. No error is displayed, but nothing happens.
6. When I open an LDAP user account for editing, all the information is missing. The first name, last name and mailing address that appear in the listing on the Users page come up empty. The first time I do this the roles that I have set previously on the Users page are also missing.
7. When I open an LDAP user account for editing, the reset password option is available if the user has no email address, but is not available if they have an email address. Is this not backwards?
I have investigated this a bit and I found:
1. The sf_manager_info table did not have any entries for AgentMember. And sf_users gave the same manager_info guid to all its rows.
2. I added three records into sf_manager_info table matching the records for "Default" except with new Guids and Timestamps for Agent Member. After this the sf_users table had the right value for manager_info.