Jump to content

Search the Community

Showing results for tags 'radius'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 8.x
    • General Support
    • Feature Requests
    • Feature Requests - Completed
    • Known Issues
    • Installing Passwordstate
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • Mobile Client
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 7.x
    • General Support
    • Known Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 1 result

  1. The current implementation of RADIUS only allows the use of tokens/passwords that do not require a challenge/response. Currently, if a RADIUS Challenge message is sent to the portal, a Password Incorrect message is instead shown. Example Scenario [RADIUS server setup to use SMS tokencodes]: User enters their PIN and clicks Next PIN is sent to RADIUS server RADIUS server responds with Access-Challenge message Password portal prompts user for next token code (or whatever message is sent back with the Access-Challenge) User enters tokencode they received and clicks Next RADIUS server respondss with Access-Granted and authentication succeed This is also useful in scenarios when using hardware/software tokens via RADIUS and a PIN rotation is enabled. The portal would need to be able chain Access-Challenge responses as there may be more than one.
×