https://github.com/ebyte23/samlsilly
SAMLSilly is a new simple valid implementation of the SAML 2.0 Standard
https://github.com/ebyte23/samlsilly
asp-net asp-net-core aspnetcore dotnet dotnet-core saml saml-sp-single-sign-on saml2
Last synced: 10 months ago
JSON representation
SAMLSilly is a new simple valid implementation of the SAML 2.0 Standard
- Host: GitHub
- URL: https://github.com/ebyte23/samlsilly
- Owner: eByte23
- Created: 2016-08-25T00:48:56.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2022-08-11T21:18:29.000Z (almost 4 years ago)
- Last Synced: 2025-08-01T08:51:49.724Z (10 months ago)
- Topics: asp-net, asp-net-core, aspnetcore, dotnet, dotnet-core, saml, saml-sp-single-sign-on, saml2
- Language: C#
- Size: 1.7 MB
- Stars: 4
- Watchers: 1
- Forks: 1
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SAMLSilly
## What is SAMLSilly
SAMLSilly is a SAML2.0 implementation for .net and .net core (coming soon). This library was forked form [elerch/SAML2](https://github.com/elerch/SAML2) original to [eByte23/SAML2.DotNet35](https://github.com/eByte23/SAML2.DotNet35) to make it run on .net 35 and to make some large changes to the way it handles ADFS (Active Directory Federation Services). The code has diverged past the point of a merge back thus this repository.
## Documentation
Current there is no documentation for SAMLSilly. It will becoming in the future but for now is not availble.
For general SAML documentation and implmentation steps/details see [SAML.DOCS](https://github.com/eByte23/SAML.DOCS)
### Build Statuses:
master | dev | vnext
-------|-----| ------
[](https://ci.appveyor.com/project/eByte23/samlsilly/branch/master) | [](https://ci.appveyor.com/project/eByte23/samlsilly/branch/dev/current)| [](https://ci.appveyor.com/project/eByte23/samlsilly/branch/vnext)
### NOTE: When using >= SHA256 SignatureType
When using SHA256 and above you must ensure you load your certificate using X509KeyStorageFlags.Exportable | X509KeyStorageFlags.MachineKeySet flags.
If you do not do this you well get an exception like...
```System.Security.Cryptography.CryptographicException : Key not valid for use in specified state.```
For example
```
var certificate = new X509Certificate2(@"C:\My\Certificate\Path\cert.pfx", "mysuperduperpassword", X509KeyStorageFlags.Exportable | X509KeyStorageFlags.MachineKeySet);
config.ServiceProvider.SigningCertificate = certificate;
```