Note that there are some explanatory texts on larger screens.

plurals
  1. POServer communication of RSA new pin mode using RADIUS
    text
    copied!<p>I'm implementing RADIUS authentication procedure on a client in a java application.</p> <p>The RADIUS Server uses <a href="https://en.wikipedia.org/wiki/SecurID" rel="nofollow noreferrer">RSA SecurID</a> to authenticate the users. As known <a href="https://en.wikipedia.org/wiki/SecurID" rel="nofollow noreferrer">RSA SecurID</a> uses a token. When a user forgets his pin for the token, the token can be set to a special new pin mode on the server which forces the user to set a new pin on the next login attempt.</p> <p>As fas as I know the communication workflow with the server would look like the following:</p> <ol> <li>Client: Send Access-Request Package to the Server with the usual attributes.</li> <li>Server: Reply with a package indicating the special new pin mode</li> <li>Client: Display an Interface to the user to enter a new pin. Send a package to the server containing the new pin.</li> <li>Server: Reply with a Package saying that the pin has been successfully set.</li> <li>Client: Display a confirmation message and ask the user for a new passcode which he created using the new pin on his token. I assume this is basically the same package as in step 1.</li> <li>Server: Reply with an Access-Accept package if OK or and Access-Reject if Not-OK</li> </ol> <p>For step 2, 3, 4 and 5 I do not know how the package structure looks like and therefore cannot implement any logic on the client. Has anyone knowledge about the Server communication with a token is in new pin mode?</p> <p>Cheers Simon</p> <p>The tokens used look like this. To create a valid passcode you need to first type your PIN and hit the diamond key below the 7:</p> <p><a href="http://www.comprosec.ch/fileadmin/images/rsa/securid/SD520_450x297_72dpi_crop.jpg" rel="nofollow noreferrer">this http://www.comprosec.ch/fileadmin/images/rsa/securid/SD520_450x297_72dpi_crop.jpg</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload