New-PASSession not working after changing RADIUS server

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

New-PASSession not working after changing RADIUS server

L1 Bithead

I have a powershell script I give to my administrators. I use the following to authenticate:

 

Function Get-PASLogin 

{

  $caLogin = Get-credential -Message "Enter your CyberArk login credentials (Username, PIN)"

  $secureotp = Read-Host("Enter OTP") -AsSecureString

  $otp = [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($secureotp))

  Try 

  {

    New-PASSession -Credential $caLogin `

    -BaseURI https://[PVWA URL] `

    -type RADIUS `

    -OTP $OTP `

    -OTPMode Append

     

  }

  Catch

  {

    Write-Host "Incorrect Credentials. Enter your Username and PIN, followed by your OTP." -ForegroundColor Red

    Get-PASLogin

  }

}

 

This worked well & had no problems in the past. Recently, our primary RADIUS server was updated wrong and corrupted. I removed that RADIUS server from the dbparm.ini file on the vault server and while authentication in the browser is working, authentication using REST API no longer works. The only message on the vault is RADIUS authentication failure for user 'x'. No log messages show for the failure on the PVWA. Troubleshooting ideas are appreciated. I am able to authenticate in Swagger using curl and RADIUS.

5 REPLIES 5

L7 Applicator

Login using the same credentials via the PVWA web interface works? If no... check on the Radius server.

Yes, RADIUS auth works just fine from the web interface. Only having problems with RADIUS auth on the API

L2 Linker

You could open a issue for this on the psPAS github site.

 

psPAS is not something done by CyberArk but by Pete Maan.

 

https://github.com/pspete/psPAS

The successful PVWA authentication also uses append mode? where the value provided for the password is a combination of actual Password & OTP (%Password%,%OTP%)?

 

The description suggests the change to your RADIUS infrastructure/config is linked to the issue; there has been no RADIUS related changes in psPAS for some time

Correct. And I agree, but the authentication works on the PVWA and gives me a failure, and also shows as radius failure on vault logs.

  • 378 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!