A SecurID token will soon be required to use VPN
A standard set of remote access options is being deployed to all of PeopleSoft, impacting both legacy JD Edwards and legacy PeopleSoft users. As part of this standardization, the decision to require the use of a SecurID token when connecting using VPN will soon be mandatory in order to connect to the PeopleSoft corporate network.
To prepare for this change, please review the option and related document below that most closely matches your circumstance.
You do not have a token. See Eureka! document 55063 — How to request an RSA SecurID token for instructions on ordering a token.
You have a token, but are not actively using it. You should ensure the token is active and available for use. You can confirm your token is working by verifying it via the internet. For instructions, see Eureka! document 55148 — Verify SecurID token PIN via the internet.
You have a token that is not working, or you are unable to complete the verification steps. You should log a NorthStar ticket. (When logging the ticket, choose Communications, then Remote Access, then Token, and finally "I need my PIN reset." Technical Support Operations will then contact you to resolve your issue with using your SecurID token.
Created by the PeopleSoft Knowledge Management Team.
Copyright © 2004
All rights reserved.
Created: pmg 10/20/2004
Reviewed: 10/20/2004