![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, We are planning on creating a new module for an application that, while a part of that application, will be seperate from it for simplicity sake. I am confused as to what it means for an application to be authenticated for use with a database. Does this have any bearing with our license of SQL Anywhere? Or is the purpose to protect the data from access by an unauthorised application? Thanks, Sohaib |
#3
| |||
| |||
|
|
On Feb 25, 7:17*pm, Sohaib Uthmani <sohaib.uthm... (AT) googlemail (DOT) com wrote: Hi, We are planning on creating a new module for an application that, while a part of that application, will be seperate from it for simplicity sake. I am confused as to what it means for an application to be authenticated for use with a database. Does this have any bearing with our license of SQL Anywhere? Or is the purpose to protect the data from access by an unauthorised application? Thanks, Sohaib I believe what you are referring to means you have to authenticate your connections before you can use them. *I.E. "SET TEMPORARY OPTION CONNECTION_AUTHENTICATION = 'company=my_company;application=my_application;sig nature=000aab...longhexnu*mber... 1'; This is necessary for the oem edition usually for when sybase is embedded within an application. |
![]() |
| Thread Tools | |
| Display Modes | |
| |