Problems trying to migrate/build using OpenSAML3 (3.3.0) with Eclipse and Maven
Brent Putman
putmanb at georgetown.edu
Mon Feb 25 21:34:55 EST 2019
On 2/25/19 4:36 PM, o haya wrote:
> Hi,
>
> I think that I've made some (a little) progress. I am now able to do the assertion.setSignature(signature) without the app blowing up, BUT:
>
> - in order to do that, I had to add xmltooling 1.4.4 to the dependencies (see below) and
No, don't add xmltooling, nor openws. Those are part of the v2
library. The aren't necessary for v3 and indeed will screw things up,
as you see seeing.
>
> I am kind of puzzled about needing the xmltooling, because I have seen some postings that seem to indicate that, with OpenSAML V3, I should not need xmltooling?
Correct
>
> However, I could not get the app to compile without the xmltooling dependency because of using references to "Configuration" and "SecurityConfiguration".
I don't know exactly what you are attempting to do with those, but I
think I said before that those interfaces/classes have completely
changed from v2.
>
> Perhaps there are supposed to be something to substitute for those in OpenSAML V3?
>
>
Absolutely, there are new classes which do all the same things that most
of v2 classes did.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20190225/e9a28800/attachment-0001.html>
More information about the dev
mailing list