Constituent Management and SSO APIs

Michael :

Adrian, when you say "the Port" do you actually mean ThePort Networks? Convio has a custom API built specifically with that company to allow Convio to serve as the master authenticator in that SSO relationship. My hunch is that much of the work that's gone into the updated public SSO API that's been mentioned else in Open recently came out of this private API work (or visa versa...).

Anyway, CARE has a relationship with ThePort and provides a social networking environment we call CARE Connections: . It's been public only a little over 2 months now, so it's still small (though growing much more rapidly than we anticpated).

We're still on the GetActive platform, so the SSO is a little kludgey since there is no such beast as an SSO API in GetActive -- I had to sort of create one myself as a hack using a combination of JavaScript, GetActive's login form and their XML Member data API. Still, it's works more or less and what doesn't should be fixed in a couple months when we complete our migration.

I would love to talk to you about your instantiation of ThePort -- feel free to contact me privately if you'd prefer: langford@care.org or look me up on CARE Connections! ()

Yes, thePort Networks is what we are setting up. We don't want to use the default SSO we get because our branding on our social network is going to be different from our regular website (and a further complication in that we have distinct communities within the social network). Anyway, for the time being, I have a kludgey solution that will work. But I think I can do away with in short order once the SSO API changes in August.