StrongAuth, Inc. Forums

[benjib98]

Hello guys,

I am currently working on a project and came across your Key Manager service, which I would like to use together with MSSQL 2000 RDMS to store the keys.Is that possible to make these two(SKMS-MSSQL) work together and if so, what changes have to be placed?My question is maybe too much, but every advice pointing to would be appreciated as I am a bit newbie but want to get my hands dirty with coding.
The requirements are the following:
-Windows XP environment
-MS SQL 2000(2005)
-.NET framework
-C# (possible Java) language

Thank you in advance

Regards

Ben

[arshadnoor]

Using StrongKey with MSSQL itself is not a big deal, Ben; the SQL scripts that create the schema are part of the installation process and all you have to do is modify them to work on MSSQL.  If you do modify them and have them working, we would appreciate your feedback and contribution towards making it easier for the next MSSQL user :-)

Since the service is platform independent, you can run this on Windows, and have any other Windows machine call this using the SKSML protocol (which is SOAP-based).  Review the website that has the details on the protocol and then write your .NET programs to call the service and then use the symmetric key that is returned according to the policy embedded in the response packet.

Alternatively, you can use the Java library (SKCL) that we provide and have your .NET programs call this library through some .NET-Java interface (not sure if such a beast exists, but if it does, it might be easier).

Finally, we do have a commercial C/C++ DLL available for sale to those who want to call the service in the native programming language.  If you are interested in that, send an e-mail to any of the e-mail addresses at www.strongauth.com and it should reach us.  Thanks.

[benjib98]

Hi arshadnoor,

Thank you for your help/advice, I am currently working on the schema to get work on MSSQL.
The result will be obviously shown on this forum, as I think this is a good learning curve for everyone, but especially for me.
Will be in touch about the result.

Regards

Ben

[benjib98]

Hi arshadnoor,

Just a question regarding the SJSAS82 configuration to connect to the MSSQL database:
should I use the default MySQL settings in the SJSAS when setting up to work with MSSQL or do I need to use different settings?
I left the Resource type as it is and changed the vendor to mssql.all the other options changed following the documentation from the web on installation.
Tried to ping the database unfortunately got a long error.
Any idea?

Ben

[arshadnoor]

While some MySQL settings are common to all databases (schema name, username, password), most other settings are not (URL, port #, and most importantly, the JDBC driver's classname).  Can you post the values that you are currently using for the classname and connection URL?  Thanks.

[benjib98]

I tried to use the mysql JDBC classname, unfortunately couldn't connect to MSSQL.I used the following settings:
name-mysqlConnectionPool
datasource classname-same as for mysql
resource type-the same as for mysql
vendor-mssql
-the port number is my server's port number, the same is with server name,database name,username,password and the URL and url is jdbc:mysql://:portnumber
The persistent manager setup is    
-jdbc/mysql
-mysqlConnectionPool and enabled
lastly added the path setting under JVM settings
As a result got the error:Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection object cannot be null

Ben

PS:I am using now jTDS third party connector for MSSQL, which works shamelessly to connect, but still getting troubles with testing CLI,probably because of differences between MSSQL and MYSQL, which I am going to share on the cli forum

[arshadnoor]

You can't use the MySQL classname and URL for MSSQL, Ben.  Each JDBC driver has its own classes created by the vendor, and likely uses different port numbers.  You need to look up the JTDS configuration and see what they recommend when configuring their driver for JDBC connectivity.