It's simple to identify and personalize

Broad support of social identities

While most businesses and organizations only want to allow the most common social identity sources (Facebook, Twitter, Yahoo!, etc.), some organizations want to offer a broader set of options. Or perhaps, a specialized identity source such as a club, user group, or community. SocialAccess makes it easy for you to do it all. It comes integrated with the most common social identity sources right out-of-the-box, as well as support for any SAML 2 or OpenID Connect compatible sources.

Application personalization

Easily tie social identities to applications and resources through an intuitive graphical interface. This allows you customize social facing applications and services.

Remote identity access

When customers log onto your SocialAccess enabled website, they're actually using their own social identity credentials stored on that site, such as Facebook, Twitter, Google, Yahoo!, etc. This means that you don't have to build and maintain your own directory full of customer identities and credentials. In addition, this also means that you don't have to support customers when they forget their password.

Customer enrollment

The identities of customers who self-register through SocialAccess can be stored in the database of your choice. This allows you to use SocialAccess to build-out your customer list and build-up what you know about them.

Connector Toolkit

SocialAccess comes with a Connector Toolkit used to build integrations with identity sources beyond what comes out-of-the-box. Using the toolkit, you can setup your site to trust any identity provider that supports SAML 2.

High reliability

The SocialAccess appliance supports cluster configurations for increased performance and reliability. To add another node to a cluster, you simply start-up another instance of the appliance and join it to an existing cluster. Once added, the new instance of SocialAccess auto-configures itself to the cluster. If a node goes down for a time requests simply go to a different node. And when the node comes back, it reinserts and updates itself automatically. Cluster node health is color coded on the main console.