вторник, 5 января 2016 г., 15:45:18 UTC+2 пользователь Cornelius Kölbel написал:
> Am Dienstag, den 05.01.2016, 04:56 -0800 schrieb :
> > воскресенье, 15 февраля 2015 г., 22:54:10 UTC+2 пользователь
qi9x...@sneakemail.com написал:
> > > Hi, I have a SafeNet server, but would like to know if it is possible to migrate to LinOTP, and continue to use the existing hardware tokens.
> > >
> > >
> > > If I export/backup the data from SafeNet, I get a text file with entries for every user/token, with fields like e.g. sccAdminSignatureMethod (DES), sccAuthenticatorId (token ID) , sccTokenKey (128 bit value in hex)
> > >
> > >
> > > Is it possible to import this into LinOTP? I could not find any info on tools that could handle data in this format.
> > >
> > >
> > > I do have a folder on the server C:\Program Files\Secure Computing\SafeWord\ImportData with many files named importAlpine, alpineUser, alpineXml, but I do not know if these represent the full number of tokens registered on the server.
> > >
> > >
> > > Thanks for your help!
> >
> > Hi! Did you migrate to LinOTP?
> >
> > @Cornelius, how I can export data from Safenet to get mentioned output?
> >
>
> Hi Vasily,
>
> what SafeNet Software are you running?
> You can not export token data from SafeNet Authentication Manager.
> The token data of the SafeNet authentication manager is encrypted in a
> not known way, containing the domain name...
> If you are running SafeWord 2008 I am not sure if the data can be
> exported.
>
> But if you still have the dat or xml file, you can use these files to
> import the token seeds.
> These files usually contain the seeds in an unencrypted way.
>
> Kind regards
> Cornelius
>
> --
> Cornelius Kölbel
>
Thank you for your reply! Yes, we are using safenet authentication manager (SAM). So we cannot decrypt tokens data and need to recreate tokens for each migrated user. Thank you for clarification!