System generated PIN'S were not being displayed properly to the end user when SecureID authentication was used with Policy Server on Solaris. If system generated PINs were being used as part of SecurId authorization, the PIN was properly generated and set as the user's new PIN. However, the user received a 500 error instead of a screen showing the new PIN. The PIN value had to be read from the Policy Server log.This is no longer an issue.
Policy Server on Solaris has been modified so that authorization through SecureID will not fail if a system generated pin is requested.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |