- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-07-2021 09:00 AM
I have successfully been able to figure out the Alternate Shell syntax for most PSM direct connections. Connecting with an Azure platform account to https://portal.azure.com or the O365 Admin portal has me stumped.
All of the connections work when initiated from the PVWA for context, so we know they work.
Based on all the documentation and other articles it should be:
alternate shell:s:psm /u CyberArk_GA@UPNSUFFIX /a portal.azure.com /c PSM-MS-AzurePortal
I have tried a variety of variations:
Still get the "1062E" can't find the account in the vault error.
Anyone solved this one?
10-19-2021 07:00 PM
After working with Support it looks like there's a regex issue regarding the "@" in the AzureAD UPN.
We were able to get a PSM Direct connection working when the pattern was:
/u username (minus the UPN suffix) /a UPN Suffix /c PSM Connector ID
However, the connector had to be modified to essentially hard-code the UPN suffix. Then the account updated in the vault to drop the UPN suffix in the account field and move the UPN suffix to the Address field.
Interesting work around, but it did work and validated a regex issue with the "@". Tried a few other delimiter options much like a PSMP connection but none worked.
Support is researching where the regex is failing.
10-19-2021 11:33 PM
"Support is researching where the regex is failing." ... That'll be some pointless research then. To my knowledge, this use-case (having an account with a username containing an @ character) was never intended, because it clearly conflicts with the syntax to use PSM direct connections using domain accounts. When you specify "psm /u user@domain /a something /c ...", PSM implicitly searches the Vault for an account that has "user" as the username and "domain" as the address... and never searches for an account that has "user@domain" as the username.
Afaik there is no solution for this, except the workaround you mentioned of rejiggering the account and plattform to work without having the @ symbol as part of the username. CyberArk just need to add the feature of making the PSM work with both use-cases.
10-20-2021 05:21 AM
We ended up rolling back the hard-coded method because it broke the CPM's ability to change/reconcile passwords in AzureAD. Without the full UPN in the Username field the CPM wasn't able to interact with AzureAD via the GraphAPI properly.
So you have to make a choice:
COME ONE SUPPORT! Figure out the "@" problem........please!!
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!

