SSO: Federation ID should not be case sensitive

This original post was 2017, 6 years on and it is still not resolved as we face exactly the same issues!

How do we get some activity on the problem?

Hi

Is there an update on when this will be addressed?

Thank you

As someone who just launched SSO I had no idea how much of a headache this would be. I am spending hours explaining to users what is happening and deleting auto-provisioned accounts so I can update to the proper case.

As someone who just launched SSO I had no idea how much of a headache this would be. I am spending hours explaining to users what is happening and deleting auto-provisioned accounts so I can update to the proper case.

Yes please - agreed! It creates a big headache and an awful amount of work for the sys admins

I came across this issue today in the process of migrating our company to WorkFront.

The fact that this issue has not been resolved is honestly very disappointing.

A unique credential such as federated ID or username should never be case-sensitive or non-unique.

I honestly hope to see some progress made here very soon.

This post has over 300 votes already and is something that should have existed from day one when the platform was released.

Agree! Bulk editing users via the SSO bulk edit was causing another layer of problems, if not more. This left me updating (and still updating) 700+ user accounts manually in my system.

HUGE MESS of a feature/integration and defiantly should be resolved ASAP!

Very much agreed!!!!!

Yes, agreed. Very time consuming. Please make this fix!

Agree, please consider ease of use for your user base. This is an unnecessary headache!