I have my own Azure App Service Site Extension, which has an xdt transform that conflicts with another 3rd-party Site Extension. Is there any way to determine the order in which xdt transforms are applied, and can I control the order?
In your app service go to D:\home\LogFiles\Transform to see the transform logs. See the application.config before and after transformation to verify if your transform is as expected. Following are steps to find the applicationhost.config. You can disable and enable extensions to further debug the sequence of transformation. Click here to read details about Site extensions.
Go to the Kudu Console
Click the 'planet' icon
Click the Config folder
Click the download button for applicationhost.config. Or you
can click the Edit button to look at it directly in the browser
It is the directory order (Directory.GetDirectories).
Here the link to the question on git:
https://github.com/projectkudu/kudu/issues/3157
What is the risk of data capture/leak from web extensions when we run accessibility insights for web tool on webpage?
I'm an engineer on the Accessibility Insights team. This is a great question, and as part of the security and compliance requirements for our product, it's one we consider as part of the threat modeling exercises our team performs for all Accessibility Insights products.
When Accessibility Insights scans a webpage, or when you enter notes or pass/fail results during an assessment, the results are stored locally on your machine using your browser's "local storage" and "IndexedDB" mechanisms for the Accessibility Insights extension origin. The browser prevents this storage from being read directly by other extensions or pages, since they do not share the same origin.
The only points where the extension exports this data are:
When you select the "Export Report" button, it will export the data (which can include snippets of the page content) to an HTML file on your local machine.
If you enable the "More export options" preview feature and then select the "Export Report" option to "Export to Codepen", we will create a POST request to https://codepen.io to create a new pen with the same data that the exported HTML report would contain.
When select the "Copy to clipboard" option for a particular issue (the copied content includes the relevant snippet of the page)
When you configure an Issue Filing database and then select a "File Issue" button, this will export data about that particular issue (which can include a snippet of relevant page content) to the specific Issue Filing URL you explicitly configured. Specifically, the extension will we open a new tab with a URL along the lines of https://github.com/your-org/your-repo/issues/new?title=GENERATED_TITLE&body=GENERATED_BODY_INCLUDING_PAGE_SNIPPET
Accessibility Insights for Web does include usage telemetry, which you can choose whether to allow either in the prompt the first time you run the extension or later in the Settings for the extension. However, even if you allow telemetry, we never transmit any personally identifiable information; in particular, we never transmit the URL being scanned, any content from the page being scanned, or any of the text content you might enter in a "failure details" or "report summary" notes prompt.
Accessibility Insights for Web is open source; we welcome anyone to review the specific data we send. If you believe we're inadvertently including something that identifies either the user or the page being scanned, please file a bug!
I would like to know if it is possible to get audit logs on only one document library or list. I wouldn't like to do it at site collection or server farm level.
Also, is it possible in the audit logs to get information for the case of editing, what the original information was before editing and the new information?
Thanks in advance,
Matrich
In List Settings (or Library Settings) choose Information Management Policy settings.
Choose the "Define a policy..." radio button and choose OK.
Check the "Enable auditing" check box and that will show the auditable events that you can enable. Choose the ones that you want to track and click OK.
As for keeping track of what changed...I believe you will be better served by versioning enabled.
Platform: MOSS 2007 on server 2008
Sharepoint is working etc...
Problem: When you search for something, it doesn't find anything, no errors.
Authentication and permissions look fine. Search service is up and running.
What could be the problem? Any checkpoints I might have missed, any bad configurations I should check, etc...?
You should start with checking the crawl log files. That will probably give some valuable information.
Also double check that the SSP is set up correctly, with a valid content source setup, valid starting addresses, schedule etc.
Make sure that no crawl rules prohibit any searches.
And lastly, no 3rd party/custom security trimmers installed that prohibit results to be shown.
Doesn't work is not a lot of use is it.
My first guess is: Have you configured the search correctly (crawl schedules, content sources etc.)
To setup search (crawl etc.) go to the Central Admin site and then to your Shared Service Provider. in the SSP Select Seearch Adminstration. in the menu on the left you can find the link "Content sources". In the following page you can select the Content Source (something like "SharePoint sites" (out of the box). selct edit in the context menu and define your crawl schedule. Then select the "start a full crawl" checkbox.
You should make sure that you've indexed your site.
I have a MOSS 07 site that is configured for anonymous access. There is a document library within this site that also has anonymous access enabled. When an anonymous user clicks on a PDF file in this library, he or she can read or download it with no problem. When a user clicks on an Office document, he or she is prompted with a login box. The user can cancel out of this box without entering a log in, and will be taken to the document.
This happens in IE but not FireFox.
I see some references to this question on the web but no clear solutions:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.windowsservices.development&tid=5452e093-a0d7-45c5-8ed0-96551e854cec&cat=en_US_CC8402B4-DC5E-652D-7DB2-0119AFB7C906&lang=en&cr=US&sloc=&p=1
http://www.sharepointu.com/forums/t/5779.aspx
http://www.eggheadcafe.com/software/aspnet/30817418/anonymous-users-getting-p.aspx
To disable login prompt opening office documents from SharePoint 2010 do the following settings in web.config
<system.webServer>
<security>
<requestFiltering allowDoubleEscaping="true">
<!-- here's where the magic happens -->
<verbs allowUnlisted="true">
<add verb="OPTIONS" allowed="false" />
<add verb="PROPFIND" allowed="false" />
</verbs>
</requestFiltering>
</security>
</system.webServer>
If Sharepoint Shared Workspace is enabled in MS Word this may prompt users with a Windows login if users do not have permissions to access or create a Shared Workspace. Do the followoing to turn this off:
Open MS Word
Go to Tools/Options
Click General Tab
Click Service Options
Click Shared Workspace
Uncheck box that says “The document is part of a Workspace or SharePoint Site.”
Click OK
Click OK
Try to hit a MS Word document from the SharePoint site.
If this resolves issue repeat steps with every MS Office program to eliminate the prompt. (Excel, PowerPoint, Visio, ect)
http://office.microsoft.com/en-us/word/HP010414641033.aspx
Unfortuantly the only work around I've found breaks some functionality for logged in users (can't upload multiple files, connect to outlook ect..)
If that is acceptable, or you want to try it and see:
In central admin > application management > application security > authentication providers select your web app and select your provider (likely "default").
Select No for client integration and save the settings.
Open your web config, find the line <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK..... and remove the verb OPTIONS.
You should no longer be asked in ie for credentials. To reverse this simply undo both changes.
If you can click cancel and it comes up the problem is...
AuthForwardServerList
http://support.microsoft.com/kb/943280
Office doesn't know the site is trusted/local so it doesn't fwd your credentials and prompts you with an opportunity to provide them. It's a feature....
If you list your site in the proper registry key it will forward your credentials which are not needed but you won't get prompted.
If you have a url rewriting module or urlscan, configure the software to send http 403 to http OPTIONS requests.
In the Sharepoint Server 2010, The solution method is a little bit changing because the new generation Sharepoint can not hold verbs in web.config. Therfore, you must change the method. First of all, you open IIS 7.0 and choose your application site. You can see many items at the middle of the screen. You choose and double click Request Filters. In the request filtres, you can see "Verbs". You can add OPTIONS and PROPFIND verbs to a deny mode. And finally test your site. Sometimes, Sharepoint needs to close Client Integration Mode of your site. If need, you can close Client Integration Mode in Central Administration.
Possible cause and resolution:
http://support.microsoft.com/kb/943280
"You are prompted to enter your credentials when you access an FQDN site from a computer that is running Windows Vista or Windows 7 and has no proxy configured"
"For example, when you open a Microsoft Office file from a Microsoft Office SharePoint site by using 2007 Microsoft Office on a Windows Vista-based client computer that has no proxy configured, you are prompted for authentication."
My guess is that the Office client is loading the underlying document template from another location where anonymous access is enabled. This also explains why you can still open the document as the Office client can also work without loading the template the document was originally created from. To see the template URL in Word 2007, enable the Developer Ribbon from Word options and click the Document Template button on the ribbon.
That doesn't seem to be it. Once of the documents in question is an Excel file, which would not use the .doc template. Also, in the Document Template dialog, it doesn't give me a url to the SharePoint template file if I create a new Word document based on it. It just says the template is "Normal." I also tried disabling the template at the document library level and it doesn't change the password situation.
When opening an Office document in IE, an ActiveX component is used to call the client application, and prompt it to open the document. In other browsers, the download is a standard hyperlink, handled by the browser.
Does this happen in search results and in standard linked columns in document libraries as well?
Using a tool like Fiddler (as referenced/suggested in your first link reference, see http://www.fiddlertool.com/fiddler/ for more info) is the only efficient way of determining the root cause of this type of issue I'm aware of. Whatever is causing this will be happening over HTTP. A debugging proxy like Fiddler will show you exactly which URL/resource is causing the request for authentication.
On a related note, are you running a recent build of the platform? It might be wise to check to make sure this issue hasn't already been addressed by MS e.g. in a hotfix. The best list of updates I'm aware of is here: http://www.harbar.net/articles/postsp1.aspx
Check this : Remove Login box when anonymous users download office document from SharePoint Site
http://www.theblackknightsings.com/RemoveLoginBoxWhenAnonymousUsersDownloadOfficeDocumentFromSharePointSite.aspx
When developing Extranet/Internet site in SharePoint you often want to allow anonymous access and this works fairly well.
But there is one are where the out of the box experience fails regarding anonymous access and that is when you allow the users to download Microsoft Office documents. In that case IE/Office pops up a couple of Login dialogs, if the user cancels out of these the document opens as expected, but you really don't want the user to have to cancel a couple of dialogs to open your documents
The problem is that office tries to be intelligent and issues a Microsoft Office Protocol Discovery request to see how much the user is allowed to do, but SharePoint responds with access denied until the users logs in.
The solution I've found is to implement a HttpModule which rejects the Microsoft Office Protocol Discovery request if the user isn't logged in and this gets rid of the Login boxes
I'm guessing that you use Windows Vista. We had this problem on Vista but not on XP.
From Microsoft: In Windows Vista, Internet Explorer uses the Web Client service when you use Internet Explorer to access a WebDAV resource. The Web Client Service uses Windows HTTP Services (WinHTTP) to perform the network I/O to the remote host. WinHTTP sends user credentials only in response to requests that occur on a local intranet site. However, WinHTTP does not check the security zone settings in Internet Explorer to determine whether a Web site is in a zone that lets credentials be sent automatically.
If no proxy is configured, WinHTTP sends credentials only to local intranet sites.
Note If the URL contains no period in the server’s name, such as in the following example, the server is assumed to be on a local intranet site:
http://sharepoint/davshare
If the URL contains periods, the server is assumed to be on the Internet. The periods indicate that you use an FQDN address. Therefore, no credentials are automatically sent to this server unless a proxy is configured and unless this server is indicated for proxy bypass.
This is a known issue that has not quite been completely fixed yet. There is a MSDN blog about it here: http://blogs.msdn.com/sharepoint/archive/2007/10/19/known-issue-office-2007-on-windows-vista-prompts-for-user-credentials-when-opening-documents-in-a-sharepoint-2007-site.aspx
There is an interesting workaround posted here: http://grounding.co.za/blogs/neil/archive/2008/11/10/workaround-sharepoint-keeps-prompting-for-login-when-creating-office-2007-documents-on-vista.aspx
Ultimately there is a patch that has been included with Vista SP1 but it also requires a registry edit. We just recently got this to work using the following steps on a Windows Vista SP2 client:
Open regedit. Navigate to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Create a new Multi-String value called AuthForwardServerList and give it a value of (for example):
https://.Contoso.com
http://.dns.live.com
*.microsoft.com
https://172.169.4.6
Then restart the WebClient service.
We were able to get this working by changing IE settings.
We have the site URL in Trusted Sites.
Under Custom Settings set User Authentication to: Automatic logon with current user name and password
I found a solution. First of all, you open the web application config file under the inetpub. Then you find the add verbs section. In this section, many verbs were added in the installation time. Delete Options and Profind verbs and save config file. Finally test the problem and see it. The problem is finished.
I've found the following workaround:
http://www.objectsharp.com/cs/blogs/max/archive/2008/04/21/sharepoint-public-facing-website-and-microsoft-office-documents.aspx
To keep it simple:
Disable client integration
Remove the OPTIONS verb from the registration line in the web.config file for the site