Hey, Since changes from 4.0.3 to 4.0.4 changed some authentication API, we had to modify our OpenAM integration library. Meanwhile we discussed opening the source of module for the community - uPortal community would benefit from having out-of-the-box OpenAM integration as alternative for CAS, but we would get closer integration with uPortal API, hence (hopefully) better change adoption from version to version.
How could we accomplish that? I remember discussing that making CAS integration code as a separate module would introduce circular dependencies... Making OpenAM integration as module would introduce the same problems. Should we create a new package (org.jasig.portal.security.provider.openam)? -- Arvīds -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
