manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lugert <>
Subject Re: Sharepoint
Date Fri, 22 Feb 2013 19:51:02 GMT
Ok thanks, installed.  Seeing these two issues now, wondering if y'all have seen these. 
I'm not a Sharepoint expert, but seems it's security is, um, difficult:
 1. Alternate access mappings have not been configured. Users or services are accessing the
site http://amazona-2h120gm with the URL
This may cause incorrect links to be stored or returned to users. If this is expected, add
the URL as an AAM response URL. For more information,
Not sure this is actually causing any issues right now, but if you've seen this let me know.
The request failed with HTTP status 401: Unauthorized.
My admin just ran the script for installing mcpermissions.asmx.  But it seems like there
is an extra step to grant users access?
From: Karl Wright <>
To:; Mark Lugert <> 
Sent: Friday, February 22, 2013 2:00 PM
Subject: Re: Sharepoint

IIS uses NTLM or Kerberos typically.  You want to configure it to use NTLM.

In 1.1 and 1.1.1 there was a problem with the NTLM implementation in
HttpClient, having to do with machines either not joined to domains or
joined to child domains.  If you think you may have that problem, you
can download a version of httpclient that works properly from .  It's version 4.2.4-SNAPSHOT.


On Fri, Feb 22, 2013 at 1:36 PM, Mark Lugert <> wrote:
> Ok will try.  This server has other web apps installed as well.  There is
> clearly a conflict or or something going on with the classpath.
> Another question though.  The Sharepoint connector uses what to
> authenticate?  Seems like it would use NTLM by default as I don't see
> anywhere basic auth being set.
> The docs kind of gloss over that part, but I'm getting
> Got an unknown remote exception accessing site - axis fault = Client, detail
> = The request failed with HTTP status 401: Unauthorized.
> using the exact same credentials I use to login via the browser.  Checking
> security log and stuff, but seems like this should be documented better.
> thanks,
> mark
View raw message