Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 39 replies
  • Subscribers 5 subscribers
  • Views 28779 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SGN Product Enhancement Suggestions

vojta

Might be a good idea to star this list early so it's in early. My wishlist

- Better AD synchronization (automated, configurable schedule, and built into MC)

- "Policy for a slider" - meaning give user the option via policy to control how fast they want to encrypt the HD. Of course if this policy is disable user cannot control that (aka today's status). Giving the users a little power will simplify the deployment of such invasive product

- Better policy stamping on the client. Today you can see "Last Received" but that's misleading as policy might not have been changed for long before that. I would rather see a hashmark or some kind of name where I could match the server policy name with the client (the date should be in the name)

:145


This thread was automatically locked due to age.
Parents
  • 0

    Hi Typhoon87,

    unfortunately, SafeGuard Easy and SafeGuard Enterprise use different methodologies to write user credentials to the eToken. The way it was done by SafeGuard Easy is extremely proprietary, based on Aladdin code we do not have, so we are not able to support this old style in SafeGuard Enterprise. I am sorry for the inconvenience you have.

    If you want to use eToken with TMS and SafeGuard Enterprise , I propose to switch from user credentials to certificates. The TMS is able to handle this situation. (I also know that the German company Netfox wrote a TMS plugin for SafeGuard Enterprise user credentials, but you still need a re-format.)

    With compliments,

    :5554
Reply
  • 0

    Hi Typhoon87,

    unfortunately, SafeGuard Easy and SafeGuard Enterprise use different methodologies to write user credentials to the eToken. The way it was done by SafeGuard Easy is extremely proprietary, based on Aladdin code we do not have, so we are not able to support this old style in SafeGuard Enterprise. I am sorry for the inconvenience you have.

    If you want to use eToken with TMS and SafeGuard Enterprise , I propose to switch from user credentials to certificates. The TMS is able to handle this situation. (I also know that the German company Netfox wrote a TMS plugin for SafeGuard Enterprise user credentials, but you still need a re-format.)

    With compliments,

    :5554
Children
No Data
Unfiltered HTML