Hello,
I am using the AAL library in our application, and we have created an authentication mechanism that leverages AAL and the Authentication Context to get an AssertionCredential, which we then use to get the string form of the assertion for our requests. Our code handles the various sorts of errors authenticating in ways that our application can recover and retry.
My problem is, in the latest 100% managed assembly delivered via NuGet, all of the constructors for AssertionCredential have been made internal. This broke most all of our unit tests, where we were mocking and returning AssertionCredential ourselves so that we could test our applications surface without having to make calls out through the AuthenticationContext.
Is there any plan in the future to make this public again, or does anyone have any guidance with how we might approach testing differently to get around this problem? I'd prefer to avoid using reflection to call the internal constructor.
Thanks!
Daniel Rouleau