January 27, 2017 at 7:32 pm #15577nikolaosinlightParticipant
If I compare OpenAM 13.5 and OpenSSO 8 custom authentication modules the interface, XML and even the default samples appears 100% identical. In fact, if I develop a OpenAM Custom Authentication Module I would compile strictly against what are clearly OpenSSO (and even appear to be earlier like Sun AM) JARs:
QUESTION: Can someone please confirm that they are identical? I know the product history just seeking confirmation from others that OpenAM and OpenSSO Custom Auth Module development is the same!
–NikolaosJanuary 28, 2017 at 11:46 am #15582Peter MajorModerator
The new versions should have introduced generics along the way and possible a few new methods. The code may still compile against the old JARs, but the behavior can be quite different (especially around 0-byte length callbacks that can now be 0 length callback definitions). The service XMLs have received a new mandatory resourceName attribute as well, so all in all: an auth module written for OpenSSO will most likely not work with OpenAM without some adjustments.January 30, 2017 at 5:58 am #15583nikolaosinlightParticipant
Thank You for that information. So it would appear that although an OpenSSO CAM may not work immediately out of the box that after several extremely “minor” adjustments (i.e. accounting for generics and perhaps some new methods, adding XML mandatory attribute and adjusting 0 length callbacks) that an OpenSSO CAM can be quite easily dropped in as an OpenAM CAM. In other words, I understand they are not identical but it appears the differences are very minor.
Would you agree with that statement?
–NikolaosJanuary 30, 2017 at 10:49 am #15586Peter MajorModerator
The changes are mostly minor, yes. If your module used old APIs (such as Netscape LDAP SDK), then you may need to rewrite a lot more things though. The basic concepts of how the authentication modules work certainly hasn’t changed.
You must be logged in to reply to this topic.