How to enable strong authorization

Released in version: 5.27

Updated in version: 2016.4.1.0

Stronger authentication has been implemented when processing transactions. The new authorization requires a Digitag key and the transactions page now has a timer of fifteen minutes that will lock you out if gone unused.

To set up configuration in SQL

In SQL, set up the proper configuration. Use the following script in the PrimacyCommon database:

TransactionAuthenticationProvider should be Primacy.TAP.FNB,

TransactionSubscriber should be Primacy.Workplace.BusinessObjects.Banking.Transactions.AuthenticationSubScribers.FNBTransactionSubscriber, TransactionAuthenticationTimeout should be 15, Authentication_

PrimaryServer should be https://10.33.8.167:8445/4TRESSSoap/services/Authenticator-70?wsdl

Domain should be FIRSTRAND

AuthenticationType should be AT_EMPOTPand ChannelCode should be CH_1624

Once this script is running, return to Primacy Workplace.

To enable new authorization

1. Click Settings > Lists > Application configuration > Transaction types.
2. Locate and double-click the transaction type that would like to enable.
   
    You can also right-click the transaction type and select Properties.
   
   
3. Under Options, click both the Requires authentication for creation? and Requires authentication for viewing? checkboxes.
4. Click Save and close.

The new authorization

1. Click Transactions > Cash transactions > Make payment. 
2. The new authorization screen will appear. It will ask for the FNB digipin in order to proceed. Enter the number and click OK.

The form will open. At the top of the screen, there is a timer, counting down from 15 minutes. Every time a field is entered, the timer will restart its countdown from 15 minutes.

 As a security feature, the form will expire and lock after 15 minutes. If it does expire, you can click Save to open the authorization window to enter the digipin again.

The following functionality is available in Primacy Workplace versions 2016.4.1.0 and above.

When a user Approves or Rejects a transaction, the strong authentication will need to be entered. A timer will start.

When a user Approves or Rejects one or more transactions from the Unposted transactions list, the stroner authentication will need to be entered once. That will apply to the list of records being approved or rejected. This also includes a timer.