Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 5 subscribers
  • Views 4195 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

Aladdin/Sophos eToken Support in SGN SGN 5.50.8.13 under Windows 7

CHansen

Hi there,

could you please provide me with information about compatibility of:

- Aladdin/Sophos eToken PRO (Java and Siemens CardOS)

- Windows 7 32/64Bit

- Windows XP 32Bit

- Aladidn/Sophos PKI Client 5.1 SP1

In the release notes in section 3.7 it says: The following smart cards/token are not supported on the Windows Vista or Windows 7 platforms: - CardOS, Siemens profile.

However, this sentence is not listed in section 3.8, that talks about Tokens, rather than SmartCards.

Best regards,

Christian

:6783


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

    Hi Typhoon87,

    we decided not to go for TMS integration because of the PKI integration in SafeGuard Enterprise. Our assumption is that TMS can handle this without us perfectly, and an interface from SGN to TMS is not really required. I agree that you may have to use multiple interfaces, but we only would do redundant stuff and always need to stay in sync with TMS improvements. This causes a lot of maintenance work on our side.

    This also influenced our decision regarding the credentials. I agree that a TMS connector will make perfect sense here, but most of the user community uses certificates anyway. Hence our decision not to go for the extra mile, so we left it to partners to do integration work if they want to. Netfox is one of them, and of course they want to sell their solution.

    Can't you use certificates for SGN 5.5x and credentials for SGE 4.5 in parallel? That should be working perfectly.

    With compliments,

    :9849
Reply
  • 0

    Hi Typhoon87,

    we decided not to go for TMS integration because of the PKI integration in SafeGuard Enterprise. Our assumption is that TMS can handle this without us perfectly, and an interface from SGN to TMS is not really required. I agree that you may have to use multiple interfaces, but we only would do redundant stuff and always need to stay in sync with TMS improvements. This causes a lot of maintenance work on our side.

    This also influenced our decision regarding the credentials. I agree that a TMS connector will make perfect sense here, but most of the user community uses certificates anyway. Hence our decision not to go for the extra mile, so we left it to partners to do integration work if they want to. Netfox is one of them, and of course they want to sell their solution.

    Can't you use certificates for SGN 5.5x and credentials for SGE 4.5 in parallel? That should be working perfectly.

    With compliments,

    :9849
Children
No Data
Unfiltered HTML