Tag Info

Hot answers tagged

7

Your choices of autentication are Classic/NTLM, Classic/Kerberos, Claims/NTLM and Claims/Kerberos. Basically your questions are: Classic or Claims, and NTLM or Kerberos. Both questions cover somewhat different concepts and have different implications, although related. There are vast amounts of documentation on both. Here's a short primer on all of this ...


2

Using NTLM over the Internet isn't desirable due to the potential of proxy servers not being able to handle NTLM authentication, but unless you're communicating with NTLMv1, generally you should be fine. If you're doing it over SSL, then you should absolutely be fine with NTLM. NTLM is less secure than Kerberos, however.


2

Definitely look into URL Rewriting. It does exactly that.


2

The Pages library is of a special type in SharePoint (template id 850), and most of the Publishing infrastructure is hardwired to it. It is possible to change the path but not without some custom development and tweaking. Removing it completely so that the pages appear to be at the root might not be possible. Another (probably much simpler) option is to use ...


2

Liam Cleary (SharePoint MVP) wrote a series of articles on this topic recently. Check out the Security section on his blog for more details: http://blog.helloitsliam.com/Lists/Categories/Category.aspx?CategoryId=11&Name=Security.


2

It is very true that apps (App Parts) load in an iFrame. That as you say will affect the SEO of the site. In classic Webparts it is up to you how you render the view (by rendering server side you will have all information on the page for the search engines to find) Regarding SEO and iFrames: Can Content in iframes Help My SEO? The short answer is ...


2

You are redirected to the Pages library instead of pages because there is a property on the web level, which holds the old URL of the default page. In order to fix this, you will need to insert the following snippet into your script: $folder = $SPWeb.RootFolder; $folder.WelcomePage = $folder.WelcomePage.Replace("Pages","pages"); $folder.Update(); I hope ...


1

Personal site on SharePoint can be a lot of fun indeed. Here I have a little inspirational article for you: Public blog on SharePoint This is my post about my own blog. I believe it has some useful tips for those who want to take same road (main advice would be: forget the SP blog template). For me, building blog on SP was a lot of fun and great ...


1

You can have Office 365 personal package which comes with a site, 1 TB one drive storage, email account and etc... Also you will be able to tryout somethings in that site as well. Also 60 Skype world minutes free. It's 7 USD per month or 70 USD per year. It depends on your requirement. If you want to maintain just a blog, buy a domain through Google or ...


1

Waldek is right, you should definitively look into Liam in depth serie. In the meantime, nothing prevent you from implementing an http module like described over there : http://share1point.blogspot.com/2012/10/httpmodule-and-sharepoint-security.html If you're not able to make distinction from all your authenticated users (eg: public and internal ...


1

SharePoint does this by default. You can, however, override the page title with jQuery: http://www.sharepointjohn.com/sharepoint-2007-jquery-to-fix-ugly-page-titles/ You could use this solution to create a custom page head control that includes your JavaScript to override the page title: ...


1

The tasks involved in making a internet facing SharePoint site depends on what you need: At a minimum you should: Get a DNS entry pointing to your site, how you get that set up depends on your hoster Enable anonymous access to the site. Here is the full process, but you may not have the rights to do the central admin part, so again you may need your ...


1

Did you use Wictor's post about Windows live authentication for integration? For restricting the users of sepcific domain, I would recommend using HttpModule to filter the requests.


1

Content translation is always a manual process. Once a variation has been created from a published page, it appears in the target variation as a draft, ready for manual translation. Ensure your list schemas and navigation nodes match your requirements before creating your variation hierarchies. Styling will always be consistent and inherit from the root ...


1

there are several ways to achieve this. Most important for public sites with SharePoint is the same like with others: hardening! So before we can start planning your publishing let's collect some further information: Which Authentication do you plan for external users? Which Firewall/Proxy product do you use in front of SharePoint (ISA, TMG, UAG, other)?


1

Check here... I've ran into this a few times and this KB has really saved me. http://support.microsoft.com/kb/896861 Cheers, Matt B.



Only top voted, non community-wiki answers of a minimum length are eligible