Troubleshooting SAML Login for CU4VDI Users

The discussion revolved around an issue with logging in via SAML for CU4VDI users. The error suggested that there were no Active Directory user accounts, even though SAML was being used. The group brainstormed possible solutions and DM’d the original poster for more specific information.

Read the entire ‘Troubleshooting SAML Login for CU4VDI Users’ thread below:

probably a dumb question but ill ask it here anyway. it seems like something has changed for CU4VDI when logging in via SAML and now I am getting this for some users. There are no Active directory user accounts since I am using SAML , but its acting like it wants to match to an AD user account. Any ideas here?

@member you any idea here SMAL is not my strongest

lol can’t even spell it right

Never seen that error before. Lets see what we can find

I assume it just means the SAML service didn’t understand how the sam account name and distinguished name would form a valid UPN

would it be that the UPN is missing from the assertion (send me to the corning if I’m better severed there)

yeah it’s there. checked with saml tracer

SAML login prefers samAccountName + distnguishedName over explicit UPN, for some reason

So the web interface sent a request to your monitors to translate the UPN into whatever format it expects. However, your monitors didn’t return any users.

DMing you since it contains some environment spefic data

Continue reading and comment on the thread ‘Troubleshooting SAML Login for CU4VDI Users’.  Not a member? Join Here!