How to Authorize RDP/Terminal Server Session for Credit Card Processing
Version: 7.5 & Up
Q: What is the best method for authorizing individual RDP/Terminal server Elliott sessions for processing credit cards?
A: You will login to that user’s window session on the terminal server, and then login to Elliott with a user (presumed to be SUPERVISOR) that has the right to access Global Setup, then perform the authorization. That is to say, for example, if your terminal server user is ABC, you would login to user ABC on this terminal server. Then start up Elliott, login as SUPERVISOR and perform the authorization this way. If you don’t have the password for user ABC, then you can shadow that user’s session while he/she logs in. Just make sure you login to Elliott as someone like SUPERVISOR (who has access to Global Setup).
The process of CC authorization is to create an encrypted key value (based on your credit card master password) in the following registry path:
\\HKEY_CURRENT_USER\Software\NETcellent\Elliott\7.0\eContact\CCSC99
The CCSC99 is a string value key where 99 represents your company ID. Different companies can have different CC master passwords, so they are represented by different entries in the registry. See sample screen below:
In theory, you could go through the CC authorization process on your own desktop and create such a key. Then use that same key to apply to the users who need to process credit cards through a group policy. That would be the most “automated” approach.
EMK