You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution `ITfoxtec.Identity.Saml2.sln` ties together three library projects stored in `src/` (core library plus ASP.NET MVC and ASP.NET Core MVC helpers). Sample and verification sites live in `test/` (e.g., `TestWebAppCore`, `TestIdPCore`, Key Vault demos) and mirror hosting models to reproduce IdP/RP conversations before publishing packages. NuGet artifacts are emitted only from the library folders; keep sample-specific assets there to avoid polluting the shipping assemblies.
5
+
6
+
## Build, Test, and Development Commands
7
+
-`dotnet restore ITfoxtec.Identity.Saml2.sln` - fetches every target framework dependency.
8
+
-`dotnet build ITfoxtec.Identity.Saml2.sln -c Release` - runs multi-targeted builds and produces signed binaries.
9
+
-`dotnet pack src/ITfoxtec.Identity.Saml2/ITfoxtec.Identity.Saml2.csproj -c Release` - prepares the NuGet package used for public releases.
10
+
-`dotnet run --project test/TestWebAppCore/TestWebAppCore.csproj` - exercises SP initiated, redirect, and post bindings locally.
11
+
12
+
## Coding Style & Naming Conventions
13
+
Use 4-space indentation, braces on new lines, and `PascalCase` for public types/members. Locals stay `camelCase`, while persistent private fields use `_camelCase`. Keep namespaces explicit (`ITfoxtec.Identity.Saml2.*`) so bindings, cryptography helpers, and MVC extensions remain discoverable. Retain XML doc comments on public APIs; warnings `1591` and `1573` are suppressed only when documentation exists. Prefer guard clauses such as `ArgumentNullException(nameof(config))` and run `dotnet format` (or the equivalent IDE formatter) before submitting work.
14
+
15
+
## Testing Guidelines
16
+
Automated coverage is minimal today, so rely on the runnable apps in `test/` for regression checks. Follow the existing `Test<Context><Host>` naming pattern for any new scenario. If you introduce formal test projects, wire them into the solution so `dotnet test ITfoxtec.Identity.Saml2.sln` succeeds. Capture manual test notes covering IdP metadata, signing certificates, Key Vault references, and RelayState expectations inside the relevant `test/*` README.
17
+
18
+
## Security & Configuration Tips
19
+
Do not commit secrets or real certificates. Sample apps should load configuration via environment variables, `dotnet user-secrets`, or Azure Key Vault, matching the `TestWebAppCoreAzureKeyVault` example. When sharing traces, sanitize assertions, entity IDs, and thumbprints. Validate new bindings against trusted IdPs (Azure AD, AD FS, NemLog-in) before merging to avoid regressions for both SP and IdP consumers.
<Description>ASP.NET MVC Core is supported by the ITfoxtec Identity SAML2 MVC Core package which helps to integrate the ITfoxtec Identity SAML2 package and add support for SAML-P and SAML 2.0 tokens.
14
14
15
+
Support .NET 10.0
15
16
Support .NET 9.0
16
17
Support .NET 8.0
17
18
Support .NET 7.0
@@ -32,10 +33,10 @@ The company name ITfoxtec has changed to FoxIDs but the components will keep the
<Description>The ITfoxtec Identity Saml2 package adds SAML-P support for both Identity Provider (IdP) and Relying Party (RP) on top of the SAML 2.0 functionality implemented in .NET.
14
14
15
+
Support .NET 10.0
15
16
Support .NET 9.0
16
17
Support .NET 8.0
17
18
Support .NET 7.0
@@ -33,17 +34,36 @@ The company name ITfoxtec has changed to FoxIDs but the components will keep the
0 commit comments