How should I communicate to RSA Master database and get user authticated using .NET application

[KishoreNalgonda]

I am planning to integrate RSA securid authentication for one of my customers,  we have existing .NET web application, the same can be accessed by intranet users. I would like to add RSA securid authentication when they authorize payment. meaning when they click on button in webpage(after logging into application) I should be able to capture RSA userid , PIN+token and get validated.

Note: My customer already using RSA securid for VPN connectivity. we wanted utilize the same RSA in application.

Do we have any RSA API which can be used for integration.

what should we do to connect to RSA Master without internet connection.

[HusseinElBaz · Accepted solution]

Hello Kishore,

Please check the below link for RSA Authentication Agent API.

RSA SecureCare Online

Please follow the below in order to access our database

1 Logon to the RSA AM 8.x local console/SSH session with ‘rsaadmin’ account.

2 cd /opt/rsa/am/utils

3 ./rsautil manage-secrets -a get com.rsa.db.dba.password -u <OC_Admin_ID> -p <OC_Admin_Password>`

       This returns the database password, e.g. com.rsa.db.dba.password: vDBh1Rb005S7nX9t304v8jy3eHFFGI

       which you will copy and paste below

   . ./rsaenv

   cd ../pgsql/bin/

   ./psql -h localhost -p 7050 -d db -U rsa_dba

      paste in DB Password, e.g. vDBh1Rb005S7nX9t304v8jy3eHFFGI

      if successful you will get the  db#  prompt

   db#

So kindly check and advise us back if there is any assistance needed from our side.

Best Regards,

[JayGuillette]

Kishore,

RSA has an agent for IIS web server (and Apache) to protect logon to URL web sites, ver. 7.1.4 uses the long standing Authentication protocol on UDP port 5500 on the any version of Authentication Manager Server from ver. 5.2 to the newly expected version 8.2 later this year, or the newer ver. 8.0 Web agent can use either the original authentication protocol on UDP port 5500, or the new authentication protocol over TCP port 5500 to an AM 8.1 SP1 server.

However you probably want to integrate our Authentication Agent API for .NET (we also have one for Java).  The slightly older Agent API ver. 8.1 SP3 uses the original authentication protocol on UDP port 5500, works great.  The newer Auth Agent API ver. 8.5 (and 8.6 soon) uses the new authentication protocol over TCP port 5500 by default, but can be configured to use UDP 5500.  Basically the UDP protocol uses proprietary RSA encryption while the newer TCP 5500 protocol uses SSL/TLS and the more standard Cipher suites you see with PKI and Certs.  Our Agent APIs come with sample code which Customer Support will help you get running, but if you need developer support integrating into your application, that requires a specific Developer Support contract in order to gain access to Developers instead of Support Engineers.

Regards,