SafeNet Resources

Jump to…

SafeNet Technical Resources

Downloads and technical information for the SafeNet Authentication Services.

Changes to SafeNet

SafeNet has gone through some major changes:

  • NetIDs will be mapped to IIDs; either identifier may be used for authentication to the same card. This will resolve issues some operating systems, applications, and platforms have had with IID <-> username translation.
  • Multiple cards per user account will now be supported.
  • True synchronization will be implemented between all three safeNet servers; any one of the three can be used as a primary host or to provide highly robust failover.

The APIs available to authenticate via SafeNet are also changing. The service will be moving to industry-standard methods and implementations for authentication. This includes many new platforms into the supported list for the service.

However, this means that RVAL will be deprecated. RVAL is the “home-grown” authentication mechanism that RUPam uses to interface with SafeNet on a few UNIX machines at the university.

In order to ease the transition, the old RVAL serverside software has been “retrofitted” to work with the new implementation. However, we intend to shut down that functionality in the future. During this transition, the systems will be speaking both RVAL and the new APIs.

Information about SafeNet tokens, licensing, troubleshooting, etc. can be found here.


These agents are used to enable applications or operating systems to authenticate using SafeNet.

Unix Agents

Agent for PAM protects PAM (Pluggable Authentication Module) enabled Solaris and Linux hosts.

Windows Agents & Plug-Ins

For Microsoft Windows Server 2000/2003.

SafeNet PremierAccess Software Development Kit (SDK)

This SDK may be used in the development of custom applications to integrate SafeNet functionality into your Windows, Solaris, or Java systems.

  • Download SafeNet Authentication SDK, version 4.0.4: zip
  • Download SafeNet Authentication SDK, version 4.0.2: tar/gzip
  • Download SafeNet Authentication SDK, version 3.2.2: exe, tar/gzip, license

Notes for RADIUS Users

Administrators running systems other than Solaris, Windows, and Java interact with the RADIUS implementation on the SafeNet servers.

The RADIUS protocol, as published by Livingston, is a method of managing the exchange of authentication, authorization, and accounting information on the network. RADIUS draft was submitted to the Internet Engineering Task Force (IETF) as a draft standard in June, 1996. RADIUS is a fully open protocol.

The SafeNet PremierAccess RADIUS Server is an authentication protocol server daemon that has been interfaced with SafeNet PremierAccess through Secure Computing’s own proprietary protocol EASSP. It supports all of the RADIUS functionality documented in Internet RFC 2138, and all functionality as documented in the SafeNet PremierAccess publications, with minor restrictions on multiple simultaneous dynamic password authenticators.

If you are interested in utilizing the SafeNet PremierAccess RADIUS Server with your systems, please contact us at SafeNet Support.

Related Articles