RE: Using MySites with Forms Authentication mode?
- From: Patrick Imboden <Patrick Imboden@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 04:46:01 -0700
Hello JOP.
Firts of all excuse my english... it mght be a little bit messy.
Anyway.
It seems like you and I have almost the same concept for the WebSite as we
have.
We would also like to do a community for users. Everything with forms
authentication.
My "MySite" is working good... for now.. I'm currently struggling with other
problems...
Like personalization and registration.
Ok.. here is what I did.
I set up a website for the front end portal called OFWI. Then i created the
sharepoint services on a NEW website called OFWISPP.
I first had the problem that I enabled OFWI with forms authetication and
left ofwispp as windows authentication. Everything seemed to be working, but
OFWI just didn't get a "MySite" Link eventhough it was assigned to the SPP
that is running under OFWISPP site.
So I enabled both sites with forms authentication.
That means.. I set on both webconfig files the connection string and the
Membership Providers and after that i went to central administration and set
the authetication type of both websites (OFWI and OFWISPP) to Forms
athentication. Both have the same ASPNet Mebership provider.
After that I also had to set my ASPNET "admin" user (That I had created with
VisualStudio Website config) as Site collection adminitrator for both
Sites... here I also had to go into the subsite /ssp/admin of the OFWISPP
website and set the Aspnet "admin" user as administration.
I then went to the OFWI website... and nothing happend..
So I decided to do an IISRESET... and "voila"... the the MySite Link was
there!... and It even Worked when I clicked on it.
Hope I could help you out with this.
"JOP" wrote:
I'm currently in the process of trying to set-up a simple Internet-facing.
MOSS 2007 installation. This is not an Extranet; rather, we are trying to use
SharePoint as the foundation of a community / collaboration environment.
To this end, we are looking at using Forms Authentication as opposed to
Active Directory. At this point, it seems that the regular
AspNetSqlMembershipProvider is quite suitable for our needs, and we've been
following the numerous guides online to get Forms Auth. up and running.
Unfortunately, things don't seem to be going all that well. This is almost
certainly because there is some sort of unspoken rule that we are blindly
ignoring, or some such; but unfortunately, beta and all, the documentation
doesn't appear all that comprehensive right now.
This is how we understand it:
We have an SSP, built on top of web application number one. This provides
numerous services, but the most important to what we are doing is the MySite
functionality.
We then have a site collection for our portal; recommendations seem to
suggest this should be connected to a whole other web application, so that's
what we've done. We'll call this web app. number two.
Now, we sucesfully changed the authentication provider on number two to
AspNetSqlMembershipProvider. This allows us to log in to the site. We also
enabled anonymous access on the portal, and this appeared to work also. I
made one of the users the site collection administrator, and despite some
false starts it would appear that administrative functions are available from
within the collection. However, the familiar MySite link appears to be
missing, presumed unavailable.
Now, when we go to administer the SSP and check up on the user profiles, the
SSP is confused - because it is connected to web app. number one, which is
still running with Windows authentication. AspNetSql users are not available
from the Wild Card People Picker, as it is only able to draw users up from
the current authentication store - in this case, still Windows.
Therefore I change web application number one to also use our AspNetSql
authentication; and from Central Administration, I am assigning an
appropriate AspNetSql user as administrator of the SSP admin site. However,
this user cannot log in, and just keeps getting the forms login page instead.
Also, the site collection on web application number two suddenly appears to
be having anonymous access woes.
Like I said; there's probably something utterly fundemental we have missed
here, but damned if I know what it is.
In terms of the kind of site we are looking to build:
* Main portal, Forms authenticated, anonymous access enabled.
* Every user gets a MySite; pref. on the same domain name.
* Numerous subsites for users to get together and collaborate.
It just doesn't seem all that complex; but the Forms Authentication seems to
have thrown an additional wrench into the works. Additionally, we could do
with a better understanding of how exactly the MySites / SSP functionality
works; but again, unfortunately, resources currently seem scarce in this
regard.
Thanks in advance to anyone that can help shed at least a little light on
the situation for us.
- JOP
- Prev by Date: Re: Problem with out-of-the-box install (tabs)
- Next by Date: Re: SPS 2003 Portal change SQL server
- Previous by thread: Re: Problem with out-of-the-box install (tabs)
- Next by thread: Wildcard Search Issues
- Index(es):
Relevant Pages
|
