Jun 3, 2010 at 4:37 AM
Edited Jun 7, 2010 at 11:05 PM
Same issues here, we have a customer requiring this portal ASAP and they want to use the SQLMembership provider. I have made following changes to the solution to support SQLMembership provider.
Updated the web.config to use SQLmembership provider instead of CRMMembership provider and added forms authentication. Modified the Login.aspx page by removing the LiveID logon control and adding the asp.net logon control. Changed the
Default.master removed the LiveID LoginStatus control, and added an asp.net loginstatus and the login view control.
So at the moment I can login as an exisiting user (created using the earlier CRM accelerator portal) but cannot register a new user, send forgotten passwords, and also does not work with the Portal Invitation mechanism. I also noticed that the earlier
portal used a Profile object to store user credentials, this no longer exists and I guess needs to be re-implemented as a custom object in the new portal. Before I installed the new portal I looked at some of these posts and got the impression that changing
the membership provider was not too difficult.
Is there anyone who has actually got this to work? If so please post up detailed instructions.
Alternatively, I may be able to convince the client to use the built in liveId authentication - but I wonder how can this ever work on a development server that is not internet facing. I have a connection to the internet, but what is
the return address i.e http://yoursite.yourdomain.com/liveid.axd. My dev site is obviously not accessable from outside our corporate domain and not sure
if I will get this dns and firewall rule past the network police. I missing the obvious here?