Shibboleth SP 3 causes issues with the Crystal Reports Runtime Engine
Damian Crawford (JCAD)
damian at jcad.co.uk
Thu Jan 21 10:06:07 UTC 2021
So essentially does that mean that any referenced component within an application that uses the same dll as Shibboleth e.g. xerces-c_3_2.dll will fail?
Our current solution therefore is to either reference a different version of the Crystal Reports runtime which uses an earlier version of that dll, which isn't really viable, or to use Shibboleth 18.104.22.168 and ISAPI.
Which presumably means going forward we would need to monitor the versions of the file being used by future releases of both products to see whether there is a compatible path to upgrade either without file conflicts?
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: 19 January 2021 15:10
To: Shib Users <users at shibboleth.net>
Subject: Re: Shibboleth SP 3 causes issues with the Crystal Reports Runtime Engine
On 1/19/21, 10:02 AM, "users on behalf of Damian Crawford (JCAD)" <users-bounces at shibboleth.net on behalf of damian at jcad.co.uk> wrote:
> The Crystal runtime does install the xerces-c_3_2.dll so I guess
> this is where the conflict is occurring...is any way around this that you can think of at this stage?
Nothing I can think of. I don't do anything to the library, it's built from source. I suspect they used a different compiler, so it's impossible for them to use mine and impossible for the SP to use theirs.
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users