Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

FBA with Client Integration

  Asked By: Nakul    Date: Oct 28    Category: Sharepoint    Views: 4919

The External Collaboration Toolkit for SharePoint allows me to install
ADAM, IIS, WSS, .Net Framework 3.0, ASP.NET onto a W2K3R2SP2 server and
allow external users to use their email address for authentication
against the ADAM store. However, one feature that does not work is
enabling FBA with Client Integration. Therefore, the context menu that
includes Edit in Microsoft Office Word or Excel is not supported and
does not function correctly. I talked to Dave Mowers at Securitay and
he suggested enabling persistent cookies. IE 7 enables persistent
cookies supposedly by adding the URL to the Trusted Sites list.
However, using this advice to enable persistent cookies using IE 7 does
not seem to do the trick.

I am all ears to another workaround or solution would be nice. I
haven't installed DotNetNuke yet, but that supposedly works with FBA and
Client Integration enabled.



13 Answers Found

Answer #1    Answered By: Maegan Ellison     Answered On: Oct 28

Persistent cookies  for FBA in SharePoint requires multiple steps - have
you also enabled  Client Integration from within SharePoint itself (this
is disabled by default for FBA) and have you selected the checkbox in
the login form which switches between persistent and non-persistent

Answer #2    Answered By: Yahaira Shannon     Answered On: Oct 28

I have enabled  the client  integration from Authentication Providers.
But I am not sure about the form. Is this in IIS on the extended
external URL using the tab for ASP.NET and selecting Edit Configuration
and selecting Authentication tab? The cookie protection is set to NONE.

Answer #3    Answered By: Doris Leach     Answered On: Oct 28

No, it's a checkbox the user must check in the FBA login form itself.
It won't appear until the client  integration is enabled.

Answer #4    Answered By: Sumitra 2004     Answered On: Oct 28

Is this the remember me u box? Because I have continued to experience not
getting the appropriate results using the "remember me" feature  either.

Answer #5    Answered By: Bhairavi Damle     Answered On: Oct 28

Yes, that is the correct checkbox. What specifically is not working when you
use that?

Answer #6    Answered By: Leeann Hull     Answered On: Oct 28

In SharePoint you enable  the creation of a persistent cookie by click the
'remember me' check box on the login page. You also have to enable client
integration when you setup the Authentication provider in the Application
management tab of Central Admin.

Answer #7    Answered By: Vaasu Radhakrishna     Answered On: Oct 28

I am not sure what is going on with my ECTS login. I do exactly as you
mentioned and what I don't understand is this.

When I turn off client  integration, I am not supposed to get the Edit in
Microsoft Office Excel feature  in the drop down. However, this is
available after disabling Client Integration. I turn off Client
Integration in Authentication Providers and make sure I am pointing to
the extended web app and I still get the feature. It is almost as if
Client integration  is turned on by making this feature available,
however, the remember me does not work  if I check that box.

How would I troubleshoot this problem?

Answer #8    Answered By: Brinda Bca     Answered On: Oct 28

One thing I want to point out is that I had moved the external  URL with
SSL to the Default Site to get the external URL to appear to External
Users when they have subscribed to alerts. Now when I go to
Authentication Providers the external https://mossteam.realignllc.com is
appearing in the Web Application field when I go to Authentication
Providers. I select the Extranet zone and disable client  integration
and it doesn't seem to matter. My question is this. If I moved this
URL to the Default Site in Alternate Access Mappings and the internal
URL to the Intranet zone, why is this not being revealed when I go to
Authentication Providers? I would think that the Alternate Access
Mappings change should be reflected in both locations in Alternate
Access Mappings and in Authentication Providers wouldn't you?

Answer #9    Answered By: Sheryl Velez     Answered On: Oct 28

That's the problem then. Extending a Web Application to Create a ZONE will
create an AAM, but they aren't the same thing. When you swapped the AAM
addresses around that didn't change the address  for the Zone in the
Authentication Provider. So switching around client  integration didn't help.
In general after an AAM is created by either a Web Application or a Zone you
shouldn't change the address. That's why planning the address for the default
Zone is so critical. Once its created you end up with unexpected side effects
if you try to change it.

Answer #10    Answered By: Alexandra Lewis     Answered On: Oct 28

Would this also help with FBA users  being able to open and edit  documents within
a document library housed within a FBA publishing site?
Currently, users can neither open nor edit a document in a FBA site..

Answer #11    Answered By: Himanta Barthakur     Answered On: Oct 28

I moved the external  URL back to the Extranet zone in Alternate Access
Mappings, moved the Internal URL back to Default site. I then went to
Authentication Providers revealing the external URL in the Extranet Zone
and the internal URL in the Default Site and selected Extranet Zone,
disabled Client Integration and Saved it. I no longer have the
Edit in Microsoft Office Excel or Word function. If you move that external URL to the Default Site to fix one problem,
you actually break another in the Authentication Providers when you
attempt to disable Client Integration.

I am going to work  with this for a little bit and report my findings.

Answer #12    Answered By: Mansi Revenkar     Answered On: Oct 28

Here is exactly the same results I am experiencing as found on Codeplex.

When you use sharepoint  with forms based authentication (FBA), by
default the rich integration  points with the Microsoft Office
applications are removed. That's because in that scenario when a user
clicks the Edit in Microsoft word  menu, for example, SharePoint just
sends back the html login page instead of opening the document.
FormsBasicAuth is a custom httphandler that takes that forms based
authentication response and converts it to a basic authentication
prompt. So it comes back to the client  like a typical Windows auth basic
credentials prompt and they type in their name and password. The
credentials are validated against the default membership provider and
then the item can be opened up directly in Office. This allows you to
use FBA but still keep many of the strong integration features with the
Office desktop client.

Didn't find what you were looking for? Find more on FBA with Client Integration Or get search suggestion and latest updates.