Hi Manu 1. No. The installer only needs to be run on the development machine. It copies the binaries, example projects and documentation to the file system.
2. We support .NET 2.0 and up. Under the bin folder you'll find ComponentSpace.SAML2 DLLs and NuGet packages targeting .NET 2.0, .NET 4.0 and .NET 4.6.2. So, for example, if you're using a .NET version between .NET 4.0 and .NET 4.6.2, use the DLL or NuGet package built for .NET 4.0. If you're using a more recent version of .NET, use the DLL or NuGet package built for .NET 4.6.2 and above.
3. Once you purchase a license, you'll receive a download link for the licensed binaries. Simply replace the evaluation with the licensed, rebuild and publish your application.
As a starting point, I recommend taking a look at section 10.1 of our Developer Guide PDF. This describes the ExampleIdentityProvider and ExampleServiceProvider projects. You'll find these under the Examples\SSO\HighLevelAPI\WebForms folder. There are solution files for the various versions of Visual Studio in the Examples folder.
It's a good idea to run the ExampleIdentityProvider and ExampleServiceProvider projects in the Visual Studio debugger to see SSO in action.
The ExampleIdentityProvider demonstrates calling the SAML API as well as including SAML configuration in a saml.config file. Your client's application would need to make the same API calls and include a saml.config file but specific to your environment.
Regards ComponentSpace Development
|