Ray,

Are you injecting the profile manager via spring into your SSO solution (Filter?)? If you have a debugger attached to your environment, you might try putting a break point on the setter (or adding a log message otherwise) for the ProfileManager to make sure the system is injecting it properly. If that setter is not invoked, you are likely missing a spring configuration directive for your SSO module.

-erik

Ray, those setters are fine for injection, but you won't have them "autowired" in a plugin/SSO situation. You will need to define a spring configuration that injects the manager as part of your SSO implementation. I'll post a link to how to configure this via a plugin or jiveHome/etc file.

Ray, did you create a Spring configuration file that describes your SSO provider's dependencies, such as its dependency on the ProfileManager?

Cool. Yep, the example on how to set up an SSO filter includes an XML stanza that shows properties defined for each of the injected dependencies (managers and agents). That stanza tells Spring what will be required at run time. We have another, similar example in the topic on adding DB access to a plugin. It's not SSO or authentication, but it is about making Spring aware of a component and its dependencies.

If you're deploying your SSO provider inside a plugin, then you'll want to include a spring.xml file in the plugin (the spring.xml file goes at the root of the deployed JAR). There's higher-level information about plugin deployment in Building Plugins. If instead you're adding your SSO provider to the classpath manually, outside the plugin framework, then you'll need to put your spring.xml file in the jiveHome/etc directory of your Clearspace instance.

For other info, you might find our (small, but growing) Spring FAQ useful. Also, check out the Spring documentation on its inversion of control (IoC) container (which is what's behind dependency injection).

Finally, we have two samples you might be interested in (both in our public Subversion project). One is Erik's on doing SSO; the other does Spring stuff for database access.