Authentication Integration

[fbaptiste]

Hi,
I am currently evaluating CheckBox Web.

We need to specify our own Security Provider. You sent me samples on how to do this, but this was for Version 3.0 and these samples do not seem to work with Version 4. I have been able to compile and configure your V3 samples for V4 but it is not working properly. The Authenticate method is not being called in my custom provider (but the Initialize event of the provider is being called OK as is the constructor of the provider configurator).

Any help would be welcome.

Thanks.

[ncushing]

The provider model has been relatively unchanged for 4.0, though 4.0 allows one to specify separate authentication providers for survey taking and for the administration console.

If the ProviderData's constructor is being called, but your provider is not being instantiated, that may mean the provider is not set as the default authentication provider in SecurityConfiguration.xml. Please verify that there is only one authentication provider set as the default and that it is yours.

[fbaptiste]

That didn't work.
What's odd is when I implement Prezza.Framework.Security.IAuthenticationProvider in my authentication provider class, visual studio indicates that I must implement a public string property called x9e6af776c909c4c0.
That's not what's in the 3.0 documentation.
(Visual Studio does specify that I also need to implement an Initialize method and an Authenticate method which matches with the 3,0 docs).
I inserted file writes to debug in all methods, and I can see that the Initialize method is called as well as the property set method for x9e6af776c909c4c0, but the Authenticate method is never called.

3.0 indicates I should reference Prezza.Framework.Common.dll, Prezza.Framework.Security.dll and Prezza.Framework.Configuration.dll but I only have Prezza.Framework.dll and Prezza.Framework.Common.dll in my /bin directory. But it seems that all the namespaces I need are available through those two assemblies.

[ncushing]

I have a feeling the issue is related to the obfuscation of the code. Due to the obfuscation, some methods are probably not being called because they cannot be found by the provider factory through reflection. It seems that you may need an SDK version of the software to get the unobfuscated binaries. You can contact your sales representative to see if this is possibility.

-N