Thanks Jose,
That helps immensely. One last question/request - would it be possible to break out the IConnectionStringName interface into some sort of lightweight shared types assembly? It would be nice not to have to include multiple, heavy CS assemblies just to implement a simple interface.
(CS 2007 looks great so far, btw - much cleaner and robust than CS 2.x)
Cheers,
-Kyle
Hi Kyle,
Once I made that change last week it's something we've been looking at...and it appears likely.
(BTW, thanks for the compliments on CS2k7)
One is glad to be of service...
Is there a way to "turn off" Membership integration in a newly upgraded 2.1 to 2007 install? I have a problem with a "Role Not Found" error. Is it a setting in one of the config files?
Or, alternatively, is there a way to migrate my users, blogs with posts, and photo gallery records to a new, fresh, CS2007 install that I had create its own brand new schema?
What might be the missing "relationship" here?
MY CS install is at cs.theoblogical.org, and I have a clean, sparsely poplulated CS2007 install that I created from scratch at cs3.theoblogical.org
when you browse the the first one, you see the Role NOT Found Error
Hi
Sorry i have jumped in this conversation but i need this explained to me. I have an existing application (Personal Web site starter kit) and i need to configure CS to use that sites membership tables and thats all. The rest of CS can continue to use its own database. Can this be done or do i need the single sign on module for this.
I would like to remove the sign in area completly from CS and have my other application take care of this.
Cheers
I'm kind of confused about this also.
I currently don't have another application doing sign on (yet anyway) but I do have an existing database that I would like to use for our memembership.
From my understanding, I should be able to tie directly into this database from CS2007, which is great..... but personally, i would like to be able to log in under my own app that I'm currently developing, so that it's easier for someone to do an intial signup (since all their data is already in the database, I want to search for specific info on that user, so as to NOT duplicate user information). Because of this, apparently I have to purchase the SSO module so that they can sign in uder my app to do custom logins.
Terry Fox www.playmor.com
+1 Confused. That makes 3 confuseds in a row.
I've read every post on Morpheus, and I *still* haven't found a simple, coherent explanation of when the default CS2007 registration sharing (Morpheus) is enough and when one needs the SSO option. In another thread, I asked whether perhaps the difference is that CS2007 out of the box allows sharing of registration data but not login state with other web apps (eg. if you have an account on CS2007 you have an account on the other web app, and vice versa, but if you are logged into CS2007 you are not neccesarily logged into the other web app and vice versa), while (again, this is my working hypothesis) SSO would allow you to share login state between web apps so that if you are logged into one you are also logged into the other. No one replied to that post, so I still don't know if that guess is correct.
You are correct. I just finished integrating CS2007 with an existing app's Membership tables. CS uses the main apps DB for Membership, but when you are logged into the main app, you still have to login to CS and vice versa. Mind you, with cookie persisting, it's not a huge deal. If the userbase complains about it, I might work in an SSO module, but I doubt it will become an issue.
Sharbel: You are correct. I just finished integrating CS2007 with an existing app's Membership tables. CS uses the main apps DB for Membership, but when you are logged into the main app, you still have to login to CS and vice versa. Mind you, with cookie persisting, it's not a huge deal. If the userbase complains about it, I might work in an SSO module, but I doubt it will become an issue.
Well, right now, I could even live with having to log in twice.... but my problem is....WHERE can I find some documentation on how to use an existing database for the membership. I have looked and looked and have not had much luck finding detailed info on doing this procedure. I'm not a strong programmer, otherwise I'm sure I could figure this out on my own, but I thought that was the purpose of CS is not to have to be a strong programmer to implement a good community site, and I would think that would include being able to link to an existing user base.
Terry,
There's some good information here in these CS Bits that should be enough for you to get up and running. Jose plans on a more detailed doc on Morpheus but hasn't gotten around to it yet.
Regards,Dave
officialcommunity:At this point, everything breaks. Attempting to view any page on the CS2007 instance results in an exception: "System.Exception: A null MembershipUser is not valid to instantiate a new User".
At this point, everything breaks. Attempting to view any page on the CS2007 instance results in an exception: "System.Exception: A null MembershipUser is not valid to instantiate a new User".
I know that these posts are old, but I finally got around to implementing Morpheus with an existing membership database and I wanted to share my findings. I started from a clean install as well and I finally got it working after some trial and error. After getting the Null MembershipUser exception I came to the conclusion that it might be due to the AnonymousUser that CS creates. I manually plugged in the anonymous user and it started working...
So I decided to start over again in an effort to log my success here:
The confusing part might be in #7. Since you are running this procedure directly agains the CS store (not your target membership database) it will be creating records in the aspnet tables in the Community Server database. This sets up the proper mappings for the ADMIN and the Anonymous User during a clean install. So, as long as both databases have the 2 important "people" duplicated... I think you should be good to go.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com