From Swivel Knowledgebase Wiki

PINsafe Versions FAQ

Overview

This FAQ outlines the different features brought in by the differing versions of PINsafe. All releases contain some bug fixes and these are not generally listed below. For information on upgrading PINsafe see Upgrade PINsafe

PINsafe 3.9

In Beta Testing (not yet released)

PINsafe logs changed to save logs by date rather than number of files
Compressed log files

PINsafe 3.8.2 (4691)

released 19 March 2012

Several new transports
Option to hide password field and auto-display TURing on admin login
Fixes for SMTP transport: better HTML support, security strings working
Domain suffix no longer added twice
Bug fix: could not authenticate to PINsafe for 10 minutes after mobile client provision.
Bug fix for account unlocked message
Bug fix: timed lockout didn't work with self-reset
Bug fixes: various PositiveID issues
New user details reports for admin API
Bug fix: helpdesk users were unable to reset PINs in certain circumstances

PINsafe 3.8.1 (4256)

released 23 August 2011

Banned Credentials fixed
VoiceSage Transport timeout added
Two Stage authentication through RADIUS proxy fixed
Reprovision for Mobile Phone Client users and not dual channel users
ChangePIN policy enforcement
Invalid LDAP FQDN on usernames caused by repository switches
Case sensitivity fixes for various issues
Corrected formatting of delimited transport strings

PINsafe 3.8 (3958)

released 18 February 2011

Two Way Authentication, to send a message to the SMS gateway
Resend user credentials when their transport details change is now an option
Copy Security string to Alert allows two destinations for security strings
Transport group now defined as strings repository group
Option to use vertical security strings
Optional time based lockout for accounts
Mobile Phone App Provisioning Security restrictions
Optional Self Provision of Mobile Client
Banned PIN numbers
Custom Phone Number formatting by repository
AD Domain suffix/prefix for a repository
Check Password with Repository by XML-Agent or RADIUS NAS
Reporting within the Administration console and exportable to CSV or XML
GUI can now expand/collapse configuration options for simplification
Manual Lock, to lock an account from the Administration Console
RADIUS Proxy Option No User session to RADIUS proxy against another PINsafe instance when no session is started

PINsafe 3.7.3474

released 3 December 2009 PINsafe 3.7 software

RADIUS challenge and response
RADIUS proxy
RADIUS passing of group membership using specific vendor attributes
Use of security strings to be valid for more than one authentication
Helpdesk users can be allowed/disallowed from setting PIN's to a known value
Helpdesk users can be allowed/disallowed from adding/deleting users to the XML repository
SMS Transports "replace previous message" option is replaced by the Normal/Replace/Flash options
View a users Security Strings

PINsafe 3.6.3369

released 19 October 2009

supports IPv6
Animated Turing, PATtern, BUTton (requires Java 2.0 for animation)
Additional Single Channel parameters
Security String Index number can be requested when sending multiple security strings
LDAP browser in PINsafe Administration console
RADIUS NAS Agents can be configured to allow only certain authentication modes
XML Agents can be configured to allow only certain authentication modes
Auto PIN reset, a new PIN can be sent on account expiry
Account expiry, dates can be set when an account will expire
Idle account status, allows idle accounts to be visually identified
On Demand delivery, allows a new dual channel security string to be sent to user

Java Class paths are different to previous versions

PINsafe 3.6.3275 users should upgrade to 3.6.3369

PINsafe 3.5.2989

released December 2008

Single Channel request sessions can be shared across a PINsafe HA pair
Mark as deleted option so deleted accounts can be recovered, keeping the users PIN
Search in User Admin and usability features
Job schedules changed from cron to user friendly format
Helpdesk users can be restricted to their own repository or global
All configuration passwords are now encrypted
More than one syslog server can be defined
Stack traces are written to the log files

PINsafe 3.4.2503

released 27 May 2008

Transport Attributes setting allows transport attribute to be defined for repository
Admin/Helpdesk API to allow external applications make Create, Read, Update and Delete operations
Reporting API
Repository password checking
Audit emails for account creation and deletion
Repository Sync Jobs refinement for speed and reliability
RADIUS Vendor Group Class attribute support
OWA Integration option 'Allow non-PINsafe Users' requires PINsafe 3.4 or higher.

PINsafe 3.3.2304

released November 2007

Multiple Data Sources, such as multiple AD and LDAP data sources
Repository Groups, allowing mutiple data sources for each group
Repository Group Management user views
Repository deletion

PINsafe 3.2.1811

released 16 February 2007

External Databases can be defined, such as MySQL, MSSQL, Oracle
LDAP data source support
IP Filter lockdown for PINsafe Administration Console
Ignore AD infrastructure change option
Resend tab in user administration to send user a new PIN without knowing what the PIN is
User has no security strings bug fix

NOTE: config.xml cannot be copied from version PINsafe versions earlier than 3.2. Information must be entered manually

PINsafe 3.1.4.716

released October 2006

Agent Groups can be defined based on IP
PINless option where an OTC is sent without PIN protection for SMS or as a CAPTCHA for Single Channel
PIN Policy to prevent user choice of sequential or repeated digits
Customisable security string text
Address ranges may be specified for agents
Improved XML sync times

PINsafe 3.1.3, PINsafe 3.1.3a, PINsafe 3.1.3b, PINsafe 3.1.3c

released May 2006

Peer and Proxy against other PINsafe servers
Authentication Policies including PIN expiry, Change PIN on first login
SMTP Alerting
Syslog for PINsafe logging
Improved User Administration including user locking, searching and view by status

PINsafe 3.1.2

Rotating characters for Single Channel
Security string may now also include upper case and lower case or mixed case letters
On Demand Authentication where the security string is not automatically sent
Self Reset utility so a user can request a new PIN and unlock an account
Usernames can be case sensitive on insensitive
User Administration supports pages and includes a search facility
RADIUS support for MS-CHAP and MS-CHAPV2

PINsafe 3.1.1

User Repsository API to support repositories in addition to AD and LDAP
AD integration
MySQL database replaced by an XML repository
RADIUS supports CHAP
Administration Console redesigned
Windows GINA integration

PINsafe 2.x

PINsafe2.2.6

Agent API, AgentXML has been developed to exchange data between the Agent and the PINsafe server.
Administration Roles added
Logging and reporting
Static Password support
PINsafe MIDlet re-engineered for mobile phones updated and New Administration Pages
Updated Administration Console

PINsafe 2.1.5

Multiple Language Support
GSM MODEM support
SMTP Support for security strings
Updated and New Administration Pages

PINsafe 2.1

Variable PIN lengths (4-10 digits)
PINsafe PIN Admin System
Authentication by username supported in addition to Session ID
Licesing Added
SLIDEbar interface has been removed

PINsafe 1.4 and 2.0

RADIUS Proxy Support
PATTern and KEYpad user interfaces
Database support
Windows installer has been updated to support the use of MS SQL and Oracle.
LINUX installer has been updated to support PostgreSQL

Versions FAQ