Thanks for the reply. I opened a case and had the same answers supplied. Here is my outcome:
1) I am not trying to use both local and ldap accounts, I want to use ldap accounts, however sending the usernames to PMP in the format of <domain>\username results in the PMP "parsing" that as domain=<domain> and username = \username. The \ does not get ignored or removed no matter how I format the string being sent, and there does not appear to be a way to import users via ldap in a different format. The support person did not understand or answer this either. This has resulted in my having to revert to local accounts, which can be simply username, and sending that via SAML. Not ideal, but I had no other solution.
LDAP: DOMAIN\Adam gets interpreted as domain=DOMAIN and username=\Adam (since \Adam is not the same as Adam, it fails)
LOCAL: Adam gets interpreted as username=Adam (since it's a local account, there is no need for a domain and this works, but does not scale for a large volume of users).
2) Support had me upgrade and this now works.
3) This was also provided by support and also works.
Thanks,
Adam
1) I am not trying to use both local and ldap accounts, I want to use ldap accounts, however sending the usernames to PMP in the format of <domain>\username results in the PMP "parsing" that as domain=<domain> and username = \username. The \ does not get ignored or removed no matter how I format the string being sent, and there does not appear to be a way to import users via ldap in a different format. The support person did not understand or answer this either. This has resulted in my having to revert to local accounts, which can be simply username, and sending that via SAML. Not ideal, but I had no other solution.
LDAP: DOMAIN\Adam gets interpreted as domain=DOMAIN and username=\Adam (since \Adam is not the same as Adam, it fails)
LOCAL: Adam gets interpreted as username=Adam (since it's a local account, there is no need for a domain and this works, but does not scale for a large volume of users).
2) Support had me upgrade and this now works.
3) This was also provided by support and also works.
Thanks,
Adam