Failed to build openam post authentication plugin. about wrenam HOT 7 CLOSED

Haven't looked in-depth yet but this might help; WrenAM 13.5.0-SNAPSHOT is based on the latest OpenAM 13.5 sources we had available at the time; OpenAM 13.5.0 RC11. The ForgeRock final version of OpenAM 13.5 is basically RC17. The ForgeRock samples repo mostly likely assume 13.5.0 final. It could very well be that between RC11 and RC17 the version of some dependencies changed. So you might need to change some versions in the ForgeRock samples POM.

from wrenam.

After some investigation I think the problem is that Maven search for newer versions of local artifacts in remote repositories, following a daily frequency.

The missing dependency was already in wrensec-deps repository:
https://github.com/WrenSecurity/wrensec-deps/tree/master/repo/org/forgerock/commons/forgerock-util/3.0.1

I have to test and confirm, but I think the solution is to load again the wrensec-deps and to build wrenam project. Afterwards I'll build the post authentication sample, during the same day... :) Or with the -o (offline) option to avoid Maven remote connections.

from wrenam.

Well... I was partially wrong in my previous comment. Sorry.

The forgerock-util-3.0.1 dependency does exists in wrensec-deps BUT is not installed by the wrenam_13-5 script, it's installed by the wrenam_13 script.
Maybe adding install_artifact "org/forgerock/commons/forgerock-util/3.0.1/forgerock-util-3.0.1" in the wrenam_13-5 script will resolve the problem?

from wrenam.

The ForgeRock samples repo mostly likely assume 13.5.0 final

The sample's pom has version 14.0.0 by default, but the build instructions guides you to update that version to match your OpenAM version, in my case 13.5.0-SNAPSHOT.

from wrenam.

The only openam dependencies of the sample are the openam-core-13.5.0-SNAPSHOT and openam-shared-13.5.0-SNAPSHOT, which are built during the wrenam main build.

Again, as I pointed out in my first comment, the wrenam build was ok and all the dependencies were resolved (including the forgerock-util dependency). Then why the sample build fails if its starting dependencies are dependencies of wrenam which resolved OK , including the transitive dependencies?

Possible explanation?
What about the nearest definition first or nearest wins strategy of Maven to resolve dependencies versions?:
http://techidiocy.com/maven-dependency-version-conflict-problem-and-resolution/

from wrenam.

Thanks for looking in to it!

I do think that for the long(er) term maintaining compatibility with FR sample is not possible for Wren since OpenAM will only drifter further away from wren:AM (I doubt compatibility with Wren is an objective for FR ;-). Therefor I have forked the repo as wrenam-sample-post-auth under the WrenSecurity umbrella. Looking forward to any pull requests you might have to get this sample fixed!

Any issues related to the sample can be created in the wrenam-sample-post-auth repo. Closing this issue since it is not really related to wren:AM itself.

from wrenam.

Thanks siepkes.

Just to say that this post authentication plugin sample it's not just any sample. I think it's not the sample by itself but the wrenam/openam plugin functionality what is being tested here. The sample depends on opemam-core-13.5.0-SNAPSHOT and openam-shared-13.5.0-SNAPSHOT, both wrenam dependencies.

In my case I have a need that it's covered by the plugin functionality of wrenam/openam, and I have to adapt this sample to that need. Please see: https://forum.forgerock.com/topic/custom-ldap-attribute/

I'll continue to find a solution, working with the new repo you created. If it's not possible to fix the sample maybe I should think about adapting the corresponding wrenam code.

from wrenam.