OAUTH is a…. please wait! Before I go straight to the definition of OAUTH and its elaboration, let’s talk about few things we already know to set the context. Also, my discussion on OAuth below is very generic and is not specific to SharePoint now. Once we are clear of OAuth concepts, we will see on SharePoint OAuth implementation in another upcoming post. Apps: We all know what Apps are by now. The word App is so common now a days that I hope to see the nursery books replacing A for Apple with A for Apps Well, at least for me A is for Apps. Service: We all understand the idea of Service. A Service can be a Web Service or API that is consumed by client
Remote Event receiver is one of the two way notification options provided by the new Remote Event Infrastructure in SharePoint 2013. In SharePoint 2013, remote event receivers are built as web services and can be one-way or two-way. The remote event receivers can be registered with SharePoint 2013 just like the way local event receivers are registered in SharePoint 2010. The only difference is now we need to provide a web service URL in place of an assembly and class name. Whenever an event is raised by a SP component ( like a list or site), SharePoint calls the web service and sends the event properties to the web service which carries out its business. The web service can also call back into SharePoint, authenticated via OAuth, to read and write as needed. Below is a
SharePoint is now increasingly becoming the main collaboration and data hub in the growing enterprise world. So far, SharePoint was able to address the need of two way collaboration with External Systems : Business Connectivity Services and Search proved to be really impressive solutions to surface data from external LOB systems to SharePoint Portals. Vice-versa, External Systems were also able to surface data from SharePoint via its web services and CSOM (although in limited ways). So we see, SharePoint not only helped Organization employees to collaborate but also the Organization systems As the collaboration between SharePoint and External Systems growing day by day, there felt a need of a solid notification infrastructure in order to: Notify SharePoint when changes are made in the underlying data in the external systems. Notify External Systems when changes are
There is, of course, no need to explain over what TechEd is all about ! Still I am writing a few lines just to have a feel of it. TechEd is a grand annual event for developers and IT professionals organized by Microsoft. Every year, It is held in several locations around the world. The first TechEd was held in 1993 in Orlando, FL. By attending a TechEd, you get chance to experience the thrill of the latest and cutting edge technologies via rich presentations , interactive sessions and hands-on labs. Also, there are opportunities to meet Microsoft experts, Microsoft Most Valuable Professionals(MVPs) and other technology enthusiasts . TechEd is excellent place for enhancing the networking via parties, community areas ,interviews with industry experts, on-demand sessions and keynotes. The event
Planning a solid authentication strategy is a key part of designing robust web based solutions . Although the classic Windows or Forms authentication is still the most commonly used mode for authenticating users, it presents several challenges to developers and administrators and eventually the organizations. The classic authentication mechanisms, such as NTLM, Kerberos, and FBA has limitations that directly impact the design, implementation and maintenance of web based (including SharePoint) solutions. Specifically, the classic authentication mechanisms give rise to the below problems: In many organizations , Multiple systems (different Web Services, Websites etc) exists and generally have their own separate user repositories. As a result, multiple user repositories exists , which drastically limits the interoperability of these systems. Also, maintaining these multiple repositories can be extremely challenging because users must be added and removed