Passportal Passphrase Error

Could you verify the application Log to get the detail of the error? I'm not sure if it's an error from RDM or from PassPortal.

Regards

We are having the exact same issue, I contacted Passportal and they said it's not on their end. Devolutions developed the integration and we would need to contact them. We really need this to work. I'm on the 64bit version and nothing is showing up in the application logs. please help! :(

I will ask Hubert to check this Monday.

Regards

Hello,

Thank you for letting us know. Since we last tested the integration, PassPortal seems to have changed a few things so our test setup doesn't work anymore. We contacted them and are waiting for a response. Once we have a working test environment, we'll try and reproduce the issue.

Regards,

Thank you for the quick replies. It would be great to see an option for 2FA with Passportal included as well. From the looks of the current layout in RDM for Passportal we don't see a 2FA option and only the passphrase. Thank you.

I'm wondering if the issue with the passphrase is linked to the 2FA... either way, we'll try to add this once we can test again, assuming PassPortal's API supports 2FA setups. :)

Regards,

2FA is turned off on Passportals side for the test accounts. Sounds great, loving the support thus far. Thank you

Still looking for a solution on this, is there any further information or a time frame of when this might be fixed?

Hello,

Right now we're unable to test since we don't have any account to test with. I sent another email to one of our contacts on the Passportal team, hopefully they reply soon. Sorry about the inconvenience.

Regards,

So, good news, we have a working test setup. This means we can start working on integrating the 2FA support.

The bad news is that I'm unable to reproduce the passphrase issue. To help us debug the issue could you give me two things:

1. Your RDM application logs. They are located in the Help tab > View application logs. You can then go in the "report" tab and save it to a file and send it to me through private message here on the forum or in email at hmireault@devolutions.net

2. Go in the Help tab > Profiler. In the "debug only" tab, set the value to 1. Keep this window open and try to use your passportal credentials. You should send those logs to me the same way. They shouldn't contain any sensitive information but make sure to check beforehand.

With these I may be able to diagnose the issue better. I'm not sure what might be causing the issue since it's working perfectly on our end.

Regards,

Hello,

Sorry about the delay. Since we finally got the test setup and API documentation from Passportal, I've integrated the two factor support. It works well for us but if you find any issues please let us know.
The change will be available in the next build, RDM beta 13.0.9.0.

I still haven't been able to figure out the passphrase issue but I added more debug logging (so the #2 method). When the next RDM beta is out, if you still encounter the issue, I would like if you sent me the logs again. I'll contact Passportal's team with the result.

Regards,

Hello Hubert,

Thank you for your work so far on this. I just tried RDM beta 13.0.14.0 and we received the same error. If communicating via voice or remote access to reproduce the issue would be of any help please let me know.

Debug logs are below.

"

Double click triggered
Double click node:RDP Gateway - Desktop (rdfarm.organization.com)
--> select top 1 ID, ConnectionID, RepositoryID, UserID, State, Comment, ExpirationDate, MachineName, CreationDate, CreationUsername, CreationLoggedUserName from ConnectionState where ConnectionID = ? and State = ? and (ExpirationDate is null or ExpirationDate > ?) order by CreationDate desc : 91 ms
PassPortalHelper: RequestUser called
PassPortalHelper: Response is false
PassPortalHelper: Error message: You must provide the passphrase field
Opening in Console / Admin mode
--> INSERT INTO dbo.ConnectionLog (
[ID]
,[Username]
,[MachineName]
,[Message]
,[MessageType]
,[ConnectionName]
,[ConnectionTypeName]
,[ConnectionID]
,[ConnectionUserName]
,[StartDateTime]
,[EndDateTime]
,[StartDateTimeUTC]
,[EndDateTimeUTC]
,[GroupName]
,[Comment]
,[LoggedUserName]
,[Prompt]
,[SecurityGroup]
,[Cost]
,[Data]
,[UserInfoID]
,[SupportClose]
,[CloseMode]
,[OpenMode]
,[HostName]
,[Application]
,[Version]
,[IsEmbedded]
,[RepositoryID]
)
VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) : 204 ms

RDP - Disconnect:50331677 / exDiscReasonNoInfo
--> UPDATE dbo.ConnectionLog SET
[EndDateTime] = ?,
[EndDateTimeUTC] = ?,
[ManualEndDateTime] = ?,
[ManualClosedBy] = ?,
[CloseMode] = ?,
[ClosePrompt] = ?,
[ActiveTime] = ?
WHERE [ID] = ? : 172 ms

"

Thank you

Hello Bo,

There's something interesting in your logs:
PassPortalHelper: Error message: You must provide the passphrase field
The error message is directly returned from the Passportal API call. I'm assuming you have inputted the passphrase correctly, is that right? If so, this hints that we might not be passing the passphrase properly for some reason.

Could you give me a few more informations:
- Which endpoint are you using (canada, united states, etc)
- If you're using 2FA authentication
- Anything pertinent in regards to the login procedure that might not be default with passportal

I'll contact the passportal team for some help diagnosing the issue once you have given me the information. We must be missing something in our integration, but it's not an obvious one since it works with our account.

Regards,

We can set up an employee that has limited access for testing. Will send you the login via PM when completed. Thank you Hubert.

Hello,

To keep this thread up to date, Bo let us access their instance and we could reproduce the issue. We're currently contacting the Passportal team for assistance resolving the problem.

Regards,

Hello,

Thanks to Bo and the Passportal team's help we made a few changes to the integration and it should allow for more flexibility as well as fixing a few issues.
You'll be able to either use the default host (where you can select the endpoint only) or enter a custom URL. This is to support branded subdomains.

An important thing to note: you must enter the URL by using its regular prefix and not the "-c" version, since we can't call the API on the "-c" URL.
Example: https://NAME.mypasswordapp.com and NOThttps://NAME-c.mypasswordapp.com

This will be available in RDM 13.5.9.0.

Regards,