Hi Travis, are you using credential injection on this specific web jump?  I believe the answer is… the PRA user making the webjump connection has to provide credentails to access the host of the web browser you are attempting to launch.  If you are not using credential injection, that credential must be supplied on the front end on the connection in order to make the connection.

Example:

PRA user authenicates into the access console (local user, domain user, SSO, etc)

Selects the Web Jump Shortcut.

User is prompted for a credential to make the jump to the host device. 

User selects appropiate credential.

Connection successfull, website opened.

If this is not the behavior you are seeing, let me know.

Todd

That is the behavior we’re seeing.  I’m sure this situation is not the exact intended use for PRA, I was just hoping there was a way to allow domain users to skip having to enter credentials a second time.  We may have to look at another solution for this particular use case and leave PRA for vendor and remote IT admins.

Thank you for the response.   

Travis, to clairfy what you mean by “ hoping there was a way to allow domain users to skip having to enter credentials a second time”…

The first time they enter credentials is to log into the PRA console?

And the second time is to make the web jump connection, correct?

You do have a VAULT feature in PRA that can store a domain account and inject that account into the session.  Not certain if this fits your use case, but here is some documentation.

https://docs.beyondtrust.com/pra/docs/vault

Todd