Problems trying to migrate/build using OpenSAML3 (3.3.0) with Eclipse and Maven

[Brent Putman]

On 2/25/19 10:54 AM, o haya wrote:
> Brent,
>
> Can you explain what you mean by "For usage examples, the best thing is to look at the unit tests in the various projects."?  Where are the "various projects" that you were referring to?


The source code of each Maven project - or in the case of java-opensaml
each Maven module of the multi-modules project - will have unit tests in
a directory hierarchy underneath src/test.  That's the standard Maven
layout.  src/test/java will be the Java code and src/test/resources will
be resource files, etc for the tests.

Access to all the source code is via Git: 
https://wiki.shibboleth.net/confluence/display/DEV/Source+Code+Access

Be sure to look at the tag of the version you're actually using,  e.g.
3.4.2 for java-opensaml.  The master branch is currently being heavily
refactored for 4.x, so don't look at that.


>
> My apologies, but I am really struggling on the migration.  I have essentially been stuck at the point in the code where I have created an assertion (that part works) and am then trying to sign the assertion, and thus far, I am stuck there for several days.  If there are examples somewhere that show how to use OpenSAML V3 to sign an Assertion, given an Assertion, that would be really great!


This should give you an idea of the basics of SAML 2 Assertion signing:

opensaml-saml-impl/src/test/java/org/opensaml/saml/saml2/core/SignedAssertionTest.java

Which you can see here on the gitweb view for tag 3.4.2:

http://git.shibboleth.net/view/?p=java-opensaml.git;a=blob;f=opensaml-saml-impl/src/test/java/org/opensaml/saml/saml2/core/SignedAssertionTest.java;h=7075200cfe2ee8bc01f271228eb4aa57aedd0cf4;hb=3.4.2


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20190225/192c91be/attachment.html>