Windows Identity Foundation in SharePoint 2007 - sharepoint

I've been reading about SharePoint 2010's Claims based authentication support. At this point, my shop has several clients who may not upgrade for a while, however. In making our other services claims compatible, we're wondering if claims based authentication is realistic without a great deal of reworking of existing code in our 2007 installations?

I planned on implementing Geneva (now WIF) in MOSS 2007 last year for a blog series, but I didn't get around to it.
When I looked into it, it was entirely possible, and just required extending your SharePoint site in the same manner you would for a Forms Based Authentication provider.
If you need more info, I can go back to my notes and see if I can scrounge up some detail.
Edit
Check out this blog post for more information on setting up claims on SharePoint 2007.

Related

Using SharePoint Designer to design a SharePoint 365 (online) site?

I'm new to SharePoint development and design. Someone recommended using SharePoint Designer as a quicker way to have the site have a specific look that is different from the SharePoint Look Book. We want sections of our page to have borders with rounded edges, and specific color headers. I found several contradicting articles about using SharePoint Designer. Do you recommend using it on the latest version of SharePoint online in 2022? Have you had any success, or have you encountered any issues?
I enable scripting on my site. I tried connecting SharePoint Designer 2013 to my SharePoint online site successfully, but would like to know if it's a good idea to move forward with it.
As you can read from here SP Designer is supported on the latest On-Premises version of SharePoint(2019) on the bare minimum. But as you can see it is a product that is steadily heading to it's end-of-support/deprecation lifecycle.
Also, as you can understand, since it's development was halted since the 2013 version, a lot have changed since then, and many of the new features are not even supported by SP Designer.
If your are trying to make modifications to a SharePoint Online site, I would suggest using more modern tools(PowerApps, Power Automate, Modern UI, SPFx etc) and leaving SP Designer to it's way to deprecation.
You can also, update your question in terms of what you are trying to achieve and we could propose you some ideas :)

migrate from sharepoint 2007 too Sharepoint 2013

We have different business divisions and each division has its ecommerce site hosted as webpart in SharePoint 2007. We also have product/adv images/documents in SharePoint.
We want to migrate from SharePoint 2007 to SharePoint 2013 and as per our initial research we noted that we must first migrate to SharePoint 2010 and then to SharePoint 2013
Questions :
what is the best way to migrate from sharepoint 2007 to sharepoint 2013 considering above context. please provide pointers..
or should we re-write our webpart code in mvc and get rid of SharePoint. since we have soa arch i belive it would not be big pain to do so.. just ui webparts will be replace with mvc site
which third party migration tools can be used considering their reliability and cost.
please suggest best way to go ahead.
As you mentioned, there's not direct migration path from 2007 to 2013. It's hard to give a definitive answer without knowing more about your environment, it really comes down to trying to estimate the cost and time doing a manual migration (2007-->2010-->) versus purchasing a tool.
I have one customer that used Metalogix to go from 2007 to 2013 and it was fairly successful. They had a couple of branding issues and some code that had to be re-written to use updated API's but considering the scope of the migration, it was fairly smooth.
Ditching SharePoint and re-writing everything using MVC.... Not sure about that one. Even though you have a SOA architecture in place, it doesn't mean it will replace everything that SharePoint provides. It does a lot of things; security, service app scalability, branding, ECM, BCS, search, etc.
UI issue may be faced as below
Migration HTML content (in content webpart) from ntext data type to XML data.
SharePoint adds some extra tags for xml validation and it distorts to whole UI for all the pages. Means look and feel will not be as it is after migration.
Table based old structure in menus and drop-dwon is very hard to manage. It must be in and Box model for better UI management.
I had used Metalogix in my migration projects and it worked 70% fine, however be ready for the post deployment fixes as you might have to rewrite some scripts. But overall it works fairly good. I would also suggest you to run a report before migration using SPCAF tool.

Publish Infopath Form MANUALLY to Sharepoint

Is there a way to publish Infopath form manually? I have an infopath form that I created for sharepoint on a computer. Now, I want to move that xsn file to another dev computer where sharepoint is installed but no infopath. So, I cant use the infopath publish options. Is there a way to MANUALLY PUBLISH?
What I have tried so far is to open the xsn file and read the xsf file. That did not work.
Can someone please help me out?
Thanks,
Moving my comment to answer.
First, I did not understand what "MANUALLY" did mean... but forgot to ask.
My personal belief (from never ever sufficient experience) is that it is impossible to manually substitute the publishing (which is being done from Infopath Designer).
And the latter is proprietary undocumented about full details procedure dependent on sharepoint internals (with the latter also being proprietary and closed information).
Might be somebody else has another opinion.
Well, you can try... and report here back.
Update:
There are development suites (IDE, frameworks, extensions) where you can develop all from the scratch or use open source libraries, extensions (like .NET, MS SQL Server Business Intelligence) and the approaches where you should follow what is precompiled and closed for meddling like Sharepoint and Infopath.
There are pro and contra in both.
In any case one should analyze and balance business requirements.
Anyway, I was a little puzzled by situation when you do not have Infopath installed on client machine.
In this case, you can use Infopath forms only through Infopath Forms Services of Sharepoint Server which is enterprise and rather expensive feature.
If you (or your client have it), then Infopath (which is part of Microsoft Office suite) is usually already bundled into all Microsoft plans or packages having enterprise Sharepoint server.
There is also Office 365 (Sharepoint Online) 30-day free trials with all bundled.
Here is comparison of plans and prices.
When mine expired, I was getting warnings and proposals to buy but really continued to have access for more 4 months before my access was really cut.
It is a marketing bluff that Infopath is easy. It is easy to start by clicking a few buttons and generate something ready but this easiness pays off dearly if you will be required to do something more flexible, customizable and/or not reqadily provided OOTB (very frequently used term in Sharepoint and Infopath, Out-Of-The_Box) in Sharepoint and IP when it happens that it is more difficult, more time consuming and more involved then using development from scratch approaches

Cookiesless authentication in sharepoint

I have a sharepoint site which works on form based authentication and now I want that sharepoint site to have cookieless authentication.
Basicaly in .Net we have option in web.config to modify the session state and to make cookieless false but how do we implement the same for sharepoint sites.
Please help me in finding best solution
I'm not sure about SharePoint 2010, but SharePoint 2007 does not support cookieless authentication:
“Cookieless” Forms Based Authentication (FBA) in SharePoint 2007
So… MOSS and WSS 3.0 are both now solidly based on the ASP.NET 2.0 platform, so this should all work in a SharePoint site, right? Well, sort of. So basically, no – not at all. Once you update your web.config to use "cookieless mode" everything appears to be working at first. You authenticate, and the ticket magically appears in your URL. The problems start to appear once you begin to navigate around your site. Some URLs have the ticket in them, and some don't. It basically comes down to this – if a URL is written using a standard ASP.NET control, or if you write a relative URL yourself, the ticket is preserved and cookieless FBA works. However, if a SharePoint control writes the URL, it's absolute, the ticket is not written, and FBA breaks.
We ran this past our PSS contacts, and apparently this is a known "issue", and it's not slated to be addressed in the 3.0 product. Basically, the feature is not supported. It no doubt has something to do with SharePoint writing URLs to support Alternate Access Mappings. There's really no reason why it couldn't write them relatively, but it obviously doesn't.
You can reduce a number of cookies by using Claims Based Authentication.
You need to setup Security Token Service as described in this blog post http://blog.sharepointsite.co.uk/2010/11/change-to-session-cookies-for-claims.html
However, note that you'll lose Client Integration, as Office use cookies from IE.

What is Microsoft SharePoint? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have heard that Microsoft SharePoint was used by many companies. Could someone tell me briefly what is SharePoint and why is it popular?
What is SharePoint?
The latest version of Microsoft SharePoint software is really two different products:
Windows SharePoint Services is a free download for Windows Server. In the latest version, known as WSS v3, collaborative web sites templates include basic blog and wiki services along with list templates for Image Libraries, Document Libraries, Contact lists, Calendars, Tasks and much more.
Microsoft Office SharePoint Server 2007 or MOSS for short is built on Windows SharePoint Services. As a member of the Office Server product platform, it leverages the Microsoft Office client software to provide content on the web. Integration with Word, PowerPoint, Excel, Access and InfoPath provide rich web content from familiar content creation tools.
Why is it so popular
File Sharing
SharePoint originally became popular because it was an easy way to share documents on the web. Many organizations that adopted SharePoint in the 2003 versions capitalized on the ability to upload documents to Document Libaries and share those documents with others.
Company Extranets
One great example of this web based sharing, is a company extranet where users are not all in one location or authentication domain. Using form based authentication, accounts can be created for people across physical and company boundaries. By allowing one place for shared documents around a task rather than a corporate entity, SharePoint goes way beyond the common file share.
Content Management
There are plenty of other Content Management Systems, but MOSS incorporated the functionality of the previously name Microsoft Content Management System which itself often cost more than MOSS alone.
Search Search is greatly improved in SharePoint 2007 technologies. Search results are security trimmed, relevant and performant unlike the previous 2003 version. Bad search in SharePoint 2003 products lead to a lot of dissatisfaction with the product.
what is sharepoint
Sharepoint is really two different technologies: Windows Sharepoint Services (WSS) and Microsoft Office Sharepoint Server (MOSS). WSS is free and it comes with Windows Server 2003. MOSS isn't free.
WSS provides lots of out of the box functionality for managing documents and projects online. It manages documents in "document libraries." These are folders with permissions and different views of your documents. Projects, tasks, issues, or any tabular data, is managed in lists. Lists are similar to document libraries. They have permissions and views as well. It provides some simple search as well.
MOSS provides a better search (it's supposed to at least). It also has more publishing capabilities (WSS doesn't). And you have more control over page layouts. It's meant more for internet style sites while WSS is more for intranet sites.
and why is it popular?
WSS is popular partly because its free and partly because it just does so much out of the box. You can solve many common office requests with WSS. Stuff like issue trackers, project management and document management are trivial in WSS. That said, its a jack of all trades - good at many, master of none.
MOSS is probably less popular because its not free and having used it for a year, I don't see as much value in it as WSS. Search isn't that great. It does do a good job of creating a company directory.
I've been working with SharePoint since v.1 and I could tell you that SharePoint is a:
Document management server
Web content management server
Portal solution
Search engine
List-based repository
Collaboration site
Replacement for file shares
etc etc...
...but if I have to summarize in one sentence what SharePoint is I would say:
Sharepoint is Microsoft's Web OS.
That's real the secret of its success. Many people imagined the Web OS as something like these. A Web OS is not something that is meant to look like a desktop OS. A Web OS should be a WEB PLATFORM in which all sort of applications can be built on and users are able to collaborate with.
Think of SharePoint as the 2.0-era version of Windows :-)
Previous answers describe what sharepoint is, but don't do a good job describing why it's popular. Yes, it gives you all that neat doc-management stuff out of the box. Yes, it integrates tightly with Office.
The OOB features are 1/10th of the whole story. Sharepoint exposes a comprehensive .Net object model that lets you customize the thing to your hearts content. People are coding amazing things with MOSS 2007. With the object model, you can build and customize sites via code, in response to external events. You can write custom "web-parts" (controls hosted on special pages) that consume both internal (sharepoint) and external data.
Check out Sharepoint Blogs to see what people are doing with it.
Very good points so far but I'll try my best to add something. :)
SharePoint is not just 2 technologies. It is a set of products and technologies brought together by Microsoft into one immense product that comes in 2 flavors. The 2 flavors are Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server (MOSS). MOSS does come in standard and enterprise.
[Some of the technologies used in SharePoint: Windows Workflow Foundation, ASP.NET, Web Parts, XML (included XPath, XSLT, etc), SQL, Web Services - to name a few I can think of off the top of my head]
No matter the version you choose, SharePoint allows for web-based capabilities to allow users to create, organize, distribute, and maintain information. Because of this, the most common uses for SharePoint sites are intranets and project/team sites.
SharePoint also has incredible possibilities as an application platform. Looking at the web part and workflow pieces alone you can begin to realize the potential. For example, automation of authorization processes within an organization can quickly be developed without any code using SharePoint Designer. (FYI: more complex workflows would require Visual Studio but many simple workflows can be designed using the point and click functionality of SharePoint Designer)
While MOSS only extends upon the WSS, it does add a large amount of functionality that can be very important and useful to a business. Some of the more important features available in MOSS and not in WSS are: records management, document retention and auditing policies, browser based forms (InfoPath forms without installing InfoPath on client machine), and some of the business intelligence capabilities. Amazingly we're seeing interest in the social networking features of MOSS too. (easy to read list of features not in WSS that MOSS has)
Why is SharePoint used? I was doing some research not to long ago on this exact subject and I found a research study that cited 5 key benefits:
Ease of information access
Streamlined internal communication
Increased end-user productivity
Optimized document management practices
IT time savings
Sorry if that turned into a bit of a ramble.
It's a collaboration website. All of the members on a team can update a single calendar and upload shared documents to a single repository.
I think in this case Wikipedia have it right
Windows SharePoint Services (WSS) is the basic part of Microsoft SharePoint, offering collaboration and document management functionality by means of web portals, by providing a centralized repository for shared documents, as well as browser-based management and administration of them. It allows creation of Document libraries, which are collections of files that can be shared for collaborative editing. SharePoint provides access control and revision control for documents in a library.
In a nutshell Sharepoint is all about corporative management and collaboration features. Your company have a Windows 2003 server? Here you go. WSS 3.0 is here up and running.
SharePoint is the reason I'm considering taking advantage of a suicide booth.
In all seriousness, the rest of the answers are spot on. The differences between WSS 3.0 and MOSS 2007 commonly trip people up ("why pay for MOSS when WSS is free?" for example). SharePoint is a very complex and rich product that is integrated into other Microsoft applications, like Project Server 2007 and Team Foundation Server.
Why should you care about it? It depends. There are quite a few opportunities out there for experienced SharePoint developers and administrators. It can very quickly become the singular focus of your career if you decide to put a lot of effort into learning it.
Microsoft Office Sharepoint Server (MOSS) is a combination of two previous products, Microsoft SharePoint and Microsoft Content Management System.
It has a large number of features out of the box that are very desirable for any single system, including hosting files with customisable metadata. Page and file publishing that is enabled for end users, excellent search... the list goes on.
Essentially it is designed to enhance and organisations collaboration activities across the entire enterprise, leveraging the organistations existing Office application to create an enterprise system.
Sharepoint, MS OFFICE proxy circa 2003...
remember when you emailed a copy of that word doc out to the whole company, that's what sharepoint is for, but apparently you missed the introductory gotomeeting training course.

Resources