Single sign-on feedback required using Raiser's Edge

Gary Batchelor

I would like to identify the most appropriate method within the Raiser's Edge and associated facilities (for example, NetCommunity, Online Express, Raiser's Edge API) to meet our single sign-on requirements. 

Each of the following primary systems presents a transactional public interface. The preference is for a customer to be able to use the same logon credentials for each of these systems as this improves the consistency of services provided:

 

• Online shop
• Ticketing system
• Membership (Raiser's Edge)

We have consolidated our requirements in the form of four potential options below, with only one of which being required to be implemented:

Option 1:
Ensuring that a unique set of logon credentials can be used to authenticate customers logging on to each of the three customer-facing systems (i.e. implement single sign on across all three systems). 

Option 2:
Ensure that a unique ID can be associated with each of the customer records in the three systems (online shop, ticketing and membership) at the time of creation of a record in each system. 

Option 3:
Provide a means of routinely identifying customer records created within two or more of the three systems that potentially represent the same customer and allowing the assignment of a single ID to these records which will allow the conflation of data for CRM purposes. 

Option 4
An alternative proposition that meets the aims described.

I feel that this problem is unlikely to be unique to our company and consequently would welcome any feedback the community can bring to bear in this area.

Thank you!