Share directory and floating licencing

[soliveira]

Hi all!
I will buy a floating licensing (25), but the Sskey.dat file will stay in a shared directory and my developer team has acces to this directory (to use a licensing pool).

But any one can copy the file and use the file...
How can I block a copy of this file by a user?

Thanks!
(sorrym my english is so bad!)

[ocroquette]

The license file is linked with the drive, so you can duplicate it, but you can't move it from the original drive.

[soliveira]

Dont work... I make a copy of the file and work fine....
Have another idea?

Thanks a lot!

[dbax]

I guess you just have to trust your team.
Although I agree that floating license management from Sparx is not ideal, you can still manage it very well. In example, I made sure that the only people who can access the folder where key file resides, are the ones that do EA related work. I also made sure that they are aware of the fact that the key can be get only from that location and no copying allowed and in the installation and key retrieval guide I specifically mentioned that. Not perfect by any means but so far I had no incidents.
Regards,

D

[soliveira]

Unfortunately I cant.
I realy need to block a copy of the file.

Several companies work for me...

Any one have a solution?
Thanks all!

[ocroquette]

Are you sure the license file still works if you copy it to anotherdrive? It should not as far as I know.

Otherwise, can't you create one file per company?

[dbax]

He's right. The key does work even when the file is copied to another drive. Interestingly enough, when trying to point to another shared key file the EA prompts that current key needs to be returned (working only with one keystore) which is correct behaviour. However, when proceeding anyways and pointing to copied sskeys.dat file the OK button remains disabled which is again correct behaviour, BUT even when you click on Cancel button EA points to new keystore w/o any issues and presto - you have your own copy of EA - Corporate edition.
I believe that this might be a bug that needs to be addressed through Sparx. One suggestion to mitigate this in the short term is to embed the path of the sskeys.dat file upon its creation and if it changes do not allow retrieval of the key. Please submit this issue to Sparx.
Regards,

D

[«Midnight»]

You'll find the appropriate link at the bottom of any forum page. Depending on whether you consider the current behavior to be a bug, or the alternate behavior to be a desirable feature, you can use either the Report a Bug link, or the Feature Request link; both are found under the Support link at the bottom of the page.

Either way, please quote the title of this thread in your submission, and paste in the URL. This will allow Sparx to see what we're talking about here, and to participate in the discussion.

Also, please let us know what you hear back from Sparx on this subject.

David