Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Custom Authentication / Office 2007 Integration

  Asked By: Ralph    Date: Oct 17    Category: MOSS    Views: 767

We've implemented the IHttpModule that has allowed us to have Sharepoint
use our universities single sign on solution. The authentication part
works, we can login to Sharepoint with it and do basic features.

My problem is, Office Integration no longer appears to work. When you
click on and/or check out a Word or Excel document it pulls up in Word
or Excel but you can't save the document back to the Sharepoint server.

Questions:

1.) Do we need to implement something else to make this happen?

2.) Is there anything else other than the IHttpModule I need to be
looking into?

If we want to use Sharepoint we have to use our custom authentication
package, however if we can't save from Office to Sharepoint directly we
lose a lot of the power that our users see in Sharepoint.

Any help or advice would be greatly appreciated.

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Angarika Shroff     Answered On: Oct 17

I think you are out of luck. Office uses its own WebDav protocol to communicate
to SharePoint. Typically using custom  authentication module disables Office
Integration.

 
Answer #2    Answered By: Micheal Knight     Answered On: Oct 17

Make sure that your IHttpModule is instantiating a Windows Identity
object for the context of the sharepoint thread. Custom Authentication
normally runs SharePoint in a Generic Identity context. I've seen
problems with some Client Integration in that scenario, although that
doesn't normally keep people from saving, just using the New button.

 
Answer #3    Answered By: Lesley Tate     Answered On: Oct 17

I'll take a look into that route, thanks for the advice!

 
Answer #4    Answered By: Chris Daniel     Answered On: Oct 17

I just wanted to report back, Office Integration working with a Custom
provider... I didn't have to use the WindowsIdentity, I kept using the
GenericIdentity. The first problem was that anytime the authentication
form was editing to anything but Windows Auth Sharepoint defaulted back
to turning off Office Integration without so much as a prompt. I
flipped it back on which brought me to my second problem. When I
clicked on a Word document, Word would start and then pull up a copy of
the custom  authentication HTML page instead of the Word document...
because it was starting a new session. This is different than forms
authentication because it uses the Custom Auth app (and ours doesn't
have the ability to persist a cookie). So, what I did was build the
persisting cookie in the middle and encrypted the value contents as well
as put a time frame on it to expire. So, when the HttpModule execute's
it looks for a copy of this encrypted value, if it exists on that
machine and hasn't expired it skips the re-authentication process since
they've met our criteria. Office Integration then works.

This solution works even better for us because we don't have to worry
about how Safari and FireFox deal with NTLM and about users having to
change about:config settings in FireFox. Now, I need a nap.

 
Didn't find what you were looking for? Find more on Custom Authentication / Office 2007 Integration Or get search suggestion and latest updates.