fips={ y | n }

HTTPS, TLS

No

The fips option only supports RSA encryption.

Clients with the fips option enabled can connect to servers with the fips option disabled and vice versa.

This option can be used with end-to-end encryption. If fips is set to y, MobiLink clients use FIPS 140-2 certified implementations of RSA and AES. This option is not supported when using ECC. See e2ee_type and e2ee_public_key.

For information about how to set network protocol options with dbmlsync, see CommunicationAddress (adr) extended option.

For information about how to set network protocol options with UltraLite, see Network protocol options for UltraLite synchronization streams.

• tls_type
• e2ee_type

The following example sets up FIPS-certified RSA encryption for a TCP/IP protocol. This requires setup on the server and client. Each command must be written on one line.

On the server, the implementation is:

mlsrv12  
  -c "DSN=SQL Anywhere 12 Demo;UID=DBA;PWD=sql" 
  -x tls(
    tls_type=rsa;
    fips=y;
    identity=c:\%SQLANY12%\bin32\rsaserver.id;
    identity_password=test)

On a SQL Anywhere client, the implementation is:

dbmlsync -e 
   "CommunicationType=tls;
    CommunicationAddress=
       'tls_type=rsa;
        fips=y;
        trusted_certificate=\rsaroot.crt;
        certificate_name=RSA Server'"

In an UltraLite application written in embedded SQL in C or C++, the implementation is:

    info.stream = "tls";
    info.stream_parms = 
      "tls_type=rsa;
       fips=y;
       trusted_certificate=\rsaroot.crt;
       certificate_name=RSA Server";