Single Sign-On (SSO) and Visual Username Limitation

Hello everyone, hope someone has come up with a solution to this problem:

We are migrating to Visual 10 and have decided to use SSO. We have turned it on, but have come across a silly Visual limitation with usernames. Visual does not allow usernames with dash '-' in it

Username:BOB-GRANT
Email: bob-grant@contoson.com

These users are unable to login to Visual using SSO because of the dash character in their username.

Here are the limitations:

Visual is not allowing us to crease users with that format username. No username for BOB-GRANT
Visual does not allow custom USERNAME to Windows Security ID mapping.
- In Single Sign On Maintenance map Visual Username BOBGRANT to Windows User SID for BOB-GRANT

Visual is not allowing us to create users with that format username. Is there a fix from Visual for this silly limitation?

Find more posts tagged with

VISUAL - Enterprise General Discussions

Accepted answers

All comments

gbica

Visual usernames can only have:

Upper case A-Z

Numbers 0-9

Special characters #, $ or _

No - or . so no BOB-GRANT or BOB.GRANT or even bob

nancy-miller

Ran into this years ago... we've been lucky with our User IDs, until one wouldn't comply with Infor's restrictions. Hoping Infor devotes more attention to these types of foundational needs moving forward. Looking forward to the day where VE/IQM/SFM all use true SSO for security and authentication compliance.

gbica

I saw your post from 4 years ago, can't believe they have enabled SSO so long without a fix.

Richard Lagoy

We will be removing this limitation; I just can't tell you at what point release yet.

Infourm 2020 Feedback.docx

nancy-miller

thanks Rich.

gbica

Is there a workaround like ability to manually map Visual usernames to Windows SIDs?

systemsadmin

We started using SSO after we migrated to V10 after we could set individual users to SSO and leave others as normal; we do have some 'communal' workstations or task-based logins (rather than user-based) that don't work well that way, but we can have the best of both worlds

Fortunately our AD usernames were already pretty close to our Visual usernames, so we just adjusted the Visual ones; several major versions ago you were limited to 7-character usernames so the '#' versions of the users would be more than 8, so I just created dupe usernames for the SSO folks to match their AD login, copied settings over, delete the old user, no fuss no muss. Haven't bothered to update old records to overwrite the 'legacy' usernames, but there's no real need for us to do that yet.

Never did get the usage of Visual User Group SSO functionality to work, so we just had to do them individually in SSO maintenance, but then we don't have *that* many users.

So long story short, you can migrate your AD users to a 'Visual compatible' SSO username, depending on how complex your domain is, whether you use roaming profiles, how many places you have someone's AD username hard-coded into something, etc.

Copyright © 2025 Infor. All rights reserved.