SPAuthN 2.1.2

.NET Framework 4.5
There is a newer version of this package available.
See the version list below for details. 
dotnet add package SPAuthN --version 2.1.2
NuGet\Install-Package SPAuthN -Version 2.1.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="SPAuthN" Version="2.1.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add SPAuthN --version 2.1.2
#r "nuget: SPAuthN, 2.1.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install SPAuthN as a Cake Addin
#addin nuget:?package=SPAuthN&version=2.1.2

// Install SPAuthN as a Cake Tool
#tool nuget:?package=SPAuthN&version=2.1.2

SPAuthN - SharePoint .Net auth via Node.js

NuGet version Downloads Build Status Gitter chat

The wrapper for node-sp-auth and node-sp-auth-config for usage in .Net assemblies.

Allows authenticating in SharePoint in whatever you need scenarios and provides a wizard-like approach for building and managing connection config files.

On the first place, it is an experiment which solves one of our very specific tasks for a frontier technology stack with SharePoint/Node.js/.Net where we need running the same exactly auth mechanisms which we use in Node.js but in .Net applications. We know exactly what we're doing and why. Please use the lib only in the case when native .Net credentials strategies do not suite your app.

For whom is this library?

For folks who used to create applications for SharePoint with authentication level powered by node-sp-auth-config and node-sp-auth-config and who desire reuse authentication settings parameters and formats in .Net application.

For geeks from geeks passionated with funky technology experiments on their way doing awesome stuff.

For the cases when one tool should rule *all possible authentication strategies in SharePoint.

And definitely not for the situations when these work for you:

  • context.Credentials = new SharePointOnlineCredentials("username", "securepass");
  • context.Credentials = new NetworkCredential("username", "password", "domain");
  • Any other native authentication routes.

Versions supported

  • SharePoint Online
  • SharePoint 2019
  • SharePoint 2016
  • SharePoint 2013
  • SharePoint 2010 (limited support)

Authentication options

  • SharePoint Online:
    • User credentials (SAML/ADFS)
    • Add-In Only permissions
    • On-Demand authentication (using Electron popup)
  • SharePoint 2019, 2016, 2013:
    • User credentials (NTLM, NTLM v2)
    • ADFS user credentials
    • Form-based authentication (FBA)
    • Form-based authentication (Forefront TMG)
    • Add-In Only permissions
    • On-Demand authentication (using Electron popup)
  • SharePoint 2010:
    • User credentials (NTLM, NTMLv2)
    • Form-based authentication (FBA)
    • Form-based authentication (Forefront TMG)

Config layer and auth supports Office 365 Dedicated (SPO on custom domain) as well.

How to install

Install-Package SPAuthN

How to use

Options options = SPAuth.GetAuth();

That's it! Really!

Now options.headers object contains Cookie or Authorization which can be injected to web requests. This is a low level, session timeouts should be controlled manually.

See more on GitHub

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on SPAuthN:

Package Downloads
SPExec

SharePoint Executor The library for command line usage of SharePoint applications for deploy/retract/execute custom solutions based on CSOM (or SPMeta2 CSOM) console applications The solution that helps to execute custom code for SharePoint 2013/2016/Online based on console application (command line arguments) on different stages like deploy, retract or execute The main idea of the solution is to help to execute custom code in SharePoint in different situations and solutions and to standardize for similar solutions --- The project and details on github - https://github.com/sergeisnitko/SPExec

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.2.1 734 2/13/2020
2.2.0 569 2/13/2020
2.1.3 638 7/19/2019
2.1.2 566 6/15/2019
2.1.1 652 6/13/2019
2.1.0 2,415 4/3/2019
2.0.4 900 8/17/2018
2.0.3 2,818 3/27/2018
2.0.2 950 3/27/2018
2.0.1 1,009 2/23/2018
2.0.0 4,000 12/9/2017
1.1.4 1,240 12/5/2017
1.1.3 893 12/5/2017
1.1.2 1,430 12/1/2017
1.1.1 980 12/1/2017
1.1.0 1,259 11/30/2017
1.0.7 1,065 11/29/2017
1.0.6 1,588 11/28/2017
1.0.5 987 11/1/2017
1.0.4 974 10/30/2017
1.0.3 943 10/30/2017
1.0.2 979 10/30/2017
1.0.1 1,088 10/29/2017
1.0.0 1,267 10/28/2017

Office 365 Dedicated options added