ADFS and NOT using UPN to connect between Lawson and ADFS

Hi all, This will probably viewed as a wacky one by many of you so please bear with me.

We're in the midst of our move to ADFS (like everyone's supposed to do). Our accounts management folks are working to roll out Office 365 here and are in the midst of changing the AD UPN attribute to the user's email address. They say it's an Office 365 requirement. Our understanding is that, if they do this, we'll be forced to have folks login to Lawson using their email address which is very gross(!!). Has anyone moving to ADFS used a different AD attribute to 'connect'? Thanks very much!

Lenny

Find more posts tagged with

Comments

Legacy Contributor

Lenny - I sent you a personal message regarding this

Legacy Contributor

The answer to your question is complicated

In a simple scenario UPN is the only attribute you can use. Moreover, some Infor applications verify internally that the attribute is indeed in a UPN-like format (and that's hardcoded, so you cannot change it). However, the answer to your question is much more complicated.

For instance, if the main concern is typing the name/pwd in Mingle or Portal, you can implement ADFS mod (this is something supported by Microsoft, so it's not really a custom mod) that may allow you to add the "email portion" of the login name automatically when a user tries to login.

If the issue is related to MSCM handhelds, you can have a specially crafted service that will only work with handhelds, but will allow these users to use a different attribute.

Also, since Lawson really authenticates against SAML-accessible repository, you can make a setup where that repository has names that do not look like UPNs.

Finally, some customers implement custom AD setup, just for Infor products, and in that AD you can fill UPN values as you see fit. That setup can sync with your "main" user repository for passwords and other attributes.

In summary, you certainly have options. Some are more complex than the others to implement. If you have many users and you expect a high level of annoyance related to the changes you mentioned, you probably should consider one of the options.

Alex.

0712131256598360.doc

Legacy Contributor

Annette and Alex, Thanks for responding so incredibly quickly. Just when I think something might be straightforward I get hit over the head with reality(!). I'll pass along the info you both have sent. Have a good day!! Lenny (lc@choa.org)

Legacy Contributor

No problem. If interested in more details, let me know. We have dome quite a few of those. I may be doing a presentation on this very subject at one of the user groups in a few months.

Alex.

Copyright © 2025 Infor. All rights reserved.