Loading…
Tilbage

oiosaml.java 2.0.0


OIOSAML for Java release 2.0.0 has been made available. This release marks a series of structural changes

  • We have changed the versioning scheme from [svn-commit-id] to semantic versionering (major.minor.patch), where this is the first, with the version number 2.0.0
  • We have started using Maven as the build-tool
  • The binary artifacts are no longer distributed through digitaliser.dk, but as Maven dependencies (read more below)

Code repository

The code is still available through Softwarebørsen SVN, and can be located here

https://svn.softwareborsen.dk/oiosaml.java/oiosaml2/

Maven repository

The binary artifacts are distributed as Maven dependencies, and can be located here

https://mvnrepository.com/artifact/dk.digst/oiosaml2.java/2.0.0

Changelog

This release contains the following changes

  • improved error messaging in sitations that happens often (revoked certificates, missing strong crypto, etc etc)
  • updated to use the latest version of the OpenSAML 2.x series
  • now supports that Identity Providers uses different certificates for signing/encryption
  • support repeated claimtypes
  • improved handling of revocation checking
  • fixed all broken unittests
  • explicit handling of NETs test-environment with regard to revocation checking
  • updated demo application with valid certificates
Profilbillede

Minimum Java runtime

Mads Vering

Hvad er minimum Java runtime for OIOSAML 2.0.0?

OIOSAML 2.0.0 is build against Java 6

Profilbillede

Problems with dependencies

Peter Sone Koldkjær

I have just put the following dependency into our Ivy setup:

<!-- https://mvnrepository.com/artifact/dk.digst/oiosaml2.java -->
<dependency org="dk.digst" name="oiosaml2.java" rev="2.0.0"/>

I get:

[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :: UNRESOLVED DEPENDENCIES ::
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :: org.apache.velocity#velocity;1.7: not found
[ivy:resolve] :: commons-configuration#commons-configuration;1.10: not found
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::

I think I have my resolvers right...

[ivy:resolve] io problem while parsing ivy file: http://central.maven.org/maven2/org/apache/velocity/velocity/1.7/velocity-1.7.pom: Resetting to invalid mark
[ivy:resolve] module not found: org.apache.velocity#velocity;1.7

and

[ivy:resolve] io problem while parsing ivy file: http://central.maven.org/maven2/commons-configuration/commons-configuration/1.10/commons-configuration-1.10.pom: Resetting to invalid mark
[ivy:resolve] module not found: commons-configuration#commons-configuration;1.10

Any ideas..?

Mvh.
Peter Sone Koldkjær, mySupply ApS
Konsulent (NemHandel) for Digitaliseringsstyrelsen

Not sure exactly why you are encountering this issue.

If I try with a plain Maven pom.xml file, with only oiosaml as a dependency, and a clean local maven repository, then all dependencies resolve, and are downloaded. Could you try the same, just to check that the dependencies are resolved?

If I click on the links that your Ivy build fails on, they link to an actual file, so not sure why you cannot find the files.

Both of these seem to work fine when opening them in a browser

http://central.maven.org/maven2/org/apache/velocity/velocity/1.7/velocity-1.7.pom

http://central.maven.org/maven2/commons-configuration/commons-configuration/1.10/commons-configuration-1.10.pom

 

Perhaps it helps to clean your local repository (not sure if Ivy uses the .m2/repository folder, but if it does, then delete that and try again).

Updated Ivy to the latest version 2.4... it did the trick ;-)