Keystores

Does the Floating License Server support insecure requests (HTTP)?

No.  All communications to the Floating License Server must be made on a HTTPS port.  This is to ensure that license keys information is kept secure.

Is the Floating License Server still in development?

Yes, very much so. See the Floating License Server section in the Pro Cloud Server's release notes for the latest enhancements.

Why can't I obtain a Floating license key using Enterprise Architect? The OK button is disabled on the Add Registration Key | Get Shared Key dialog.

You have to click on an item from the 'Select a Product' list in order to enable the OK button, even when only one product is listed.

See Step 16 of the Visual Quick Start Guide.

Keys have been entered into the Floating License Server Configuration Client, but Enterprise Architect reports “No Keys Available” when trying to access - why is this?

This might indicate that you are actually accessing a different keystore to the one where your licenses have been entered.  If you are referencing the Floating License Server from Enterprise Architect (such as https://servername), make sure that you are also linking to the service from within the Floating License Server Configuration Client and not referencing a local file-based keystore (sskeys.dat).

In the Floating License Server Configuration Client application (running on the server):

• From the main menu, select 'File | Link To'
• Select 'Floating License Server / KeyStore Server' option
• then fill in the connection details: 'https' for Protocol, the 'Server Address' (localhost), Port, User Name and Password
• Click on the Test button to confirm that connection to the service is successful, then click on the OK button

If the https://localhost Floating License Server does not contain any keys, right-click on your other 'sskeys.dat' Key Store, select 'Migrate To' and specify 'https://localhost' as the destination.  After all keys have been successfully migrated, delete the 'sskeys.dat' key store from the list.  Connect to the keystore server from Enterprise Architect again and you should now be able to access your licenses.

Why can I connect to the Floating License Server via https://localhost on the same machine as where the PCS is installed, but it fails when I try to connect from another machine

Most likely requests are being stopped (as a security measure) by a Firewall or similar.  The most common reason is that Windows Firewall is enabled on the machine where your Pro Cloud Server is hosted, if this is the case you will have to add an exception to either allow incoming connections on TCP for the configured HTTPS  Port, or allow any incoming connections to the SSProCloud.exe application.

Why can't I obtain a Floating license key using Enterprise Architect? The OK button is disabled on the Add Registration Key | Get Shared Key dialog.

You have to click on an item from the 'Select a Product' list in order to enable the OK button, even when only one product is listed.

See Step 16 of the Visual Quick Start Guide.

Is the Key Store Server still in development?

No.  All functionality provided by the Key Store Server application has been moved into the Pro Cloud Server and renamed as the Floating License Server.  However the Key Store Server is still provided to Enterprise Architect customers that only want to use floating licenses and don't want to use the new features offered by the Pro Cloud Server or are not in a position to implement a SSL certificate on their server.

Does the Key Store Server support secure communications?

Unfortunately no.  The Key Store Server application was developed many years ago before secure communications became main stream.

Keys have been entered into the Keystore Manager, but Enterprise Architect reports “No Keys Available” when trying to access - why is this?

This might indicate that you are actually accessing a different key store repository to the one where your licenses have been entered.  If you are referencing the Keystore Service from Enterprise Architect (such as ssks://servername), make sure that you are also linking to the service from within the Keystore Manager and not referencing a local file-based keystore (sskeys.dat).

In the Keystore Manager application (running on the server):

• From the main menu, select 'File | Link To'
• Select 'Sparx Keystore Server' and enter 'ssks://localhost' into the 'Server Address' field
• Click on the Test button to confirm that connection to the service is successful, then click on the OK button

If the ssks://localhost Key Store does not contain any keys, right-click on your other 'sskeys.dat' Key Store, select 'Migrate To' and specify 'ssks://localhost' as the destination.  After all keys have been successfully migrated, delete the 'sskeys.dat' key store from the list.  Connect to the keystore server from Enterprise Architect again and you should now be able to access your licenses.

Why can I connect to the Keystore via ssks://localhost on the same machine as where the service is installed, but when I try to connect from another machine I see “Error: Could not connect to the Sparx Systems Keystore Service at ssks://[server address]"?

Most likely requests are being stopped (as a security measure) by a Firewall or similar.  The most common reason is that Windows Firewall is enabled on the machine where your Keystore Service is hosted, if this is the case you will have to add an exception to either allow incoming connections on TCP Port 7770, or allow any incoming connections to the KeystoreService.exe application.

Where should the Keystore file be placed?

On a shared network drive that all Enterprise Architect user have read/write access to.

Can a File based Keystore be used by users remotely?

This depends on the environment, if the remote users have connectivity to the network share that the keystore file has been placed on, then yes, otherwise no.