User experience: Ming.le as single sign-on versus direct Portal access

Would any ERP users mind sharing how the user experience is through Ming.le versus users accessing the system through the different portals has been in your organization? It seems all Ming.le discussions are happening in the Technology Group- so apologies if this is not the proper discussion board.

We are trying to understand the best practices for utilizing Ming.le as a single sign on, or utilizing the portals directly. Without going in to much technology detail, what have been the best practices for your organization in accessing the system? How positive is the user experience through Ming.le versus logging in through different domains?

We will have roughly 2600 users, right now focusing on the general user who mainly reach H.R. (landmark) and Lawson (Supply Chain). We are rolling out the system in 2017. Is anyone willing to share best practice of signing on to the different portals in the system?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

We were told that LSF10 is not supported if entry is through the Portal directly so we are going through Ming.le. User experience in my point of view is not very positive because it adds more time to the login process, when a user is trying to reach Lawson or LBI. Logging out is not easy and users have to close all browsers. That creates a big inconvenience for our shared kiosk environments. I didn't see any value added by putting Ming.le around portal. Also, The contextual apps have had very little value added and are not used by our users.

unknown

We are also using Ming.le because of support. One thing that has helped is that we created a lawprod url that goes directly into Lawson (https://<SharePointserver>/SitePages/InforSuite.aspx?LogicalID=lid://infor.lawson-s3.1). It's a little slower, but my users haven't complained. We are using some of the contextual apps, including some third party related to imaging. We only use Lawson, so I would have been perfectly happy to stay on portal. We discussed staying on portal but being fully supported was more important.

unknown

Thank you. Your comments are exactly our concern, especially the browser issue. Question: Are you only using Lawson, or do you use Global HR as well?

unknown

Thank you for the info. You answered one of our questions regarding support. One worry we have is what will happen when SharePoint 2016 is released and we update. This is helpful.

unknown

Hi! Sorry for the delayed response to your post. Here's my take (we're a hospital with 9000+ users)...

When we moved to V10 last year, our testing and what we had heard caused us great concern about now having to login via Mingle, since that's the officially supported way. We even toyed with the idea of allowing a certain population of 'superusers' to access via Portal (which is indeed very possible). We decided, for simplicity sake, to stick to one approach, having everyone go in through Mingle. As testing went on and since we've been live on V10, we haven't heard any serious complaints about Mingle/Lawson performance.

What we did learn through this process though is that Infor really does allow direct access to certain *SS functions. So, for example, we now have a direct link on our home page to Requisition Self Service (we branded it Requisition Center). That's supported by Infor. Also, for ESS/MSS, if you have that, you're allowed to build your own framework and present these tools via that. We have *not* done that.

Additionally, we're slowly but surely starting to look at Mingle Contextual Applications. These require Mingle. It'll be interesting to see how that goes but we've presented these as a 'value-add' to having users login via Mingle.

On a v10 positive note, I was, just last week, having a discussion with my manager about how stable Lawson/Landmark has been since we moved to v10. Outside of a major issue we had just after go-live of Mingle becoming accessible, which turned out to be a VMserver issue and *nothing* to do with Mingle, Lawson/Mingle/Landmark has been incredibly stable and we haven't had any other downs. It's really been quite amazing!! (I'm sure I just jinxed us!!).

By the way, we're on AIX with Oracle db and utilize all S3 modules along with LBI, MSCM, Punchout, etc.,. Outside of IPA, we don't yet have any Landmark applications. We're doing a lot with IPA flows too. Give a holler if you need additional info.

Lenny

unknown

This is very helpful. Especially the stability of the environment.

So you are suggesting that using the Ming.le is the best route for the organization, correct? I trust the judgement of someone who comes from a large organization, as we will approach roughtly 4000 users by 2018.

Especially for several portals- w are Lawson/Landmark/LSF and all of the others. We bought the entire "package," if that is the correct term- everything to support Finance, SCM, Payroll and HR. We are hosting the system locally.

unknown

Happy to help others, for sure. As to "best route" I wouldn't lay claim to our way being best practice but we decided to do what we did as the best route for us and, so far, it's working. We especially *love* the stability. Sounds like you have a huge project ahead of you. Just give a holler if you have other questions/concerns. Lenny

unknown

I know Infor does not support direct access to S3 apps via Portal but is direct access to EMSS supported? We have just started our V10 upgrade and would prefer to not burden our non IT centric EMSS users with the extra Ming.le layer if possible (but only if supported). I also understand there are different variations of the Ming.le URL one can use to access Lawson and some customers are having problems with new users logging in for the first time using certain URL's in some cases. There a more browsers supported now which I'm sure adds to the complexity. If anyone has run into this I would be very interested to hear about their findings and solutions.

Copyright © 2025 Infor. All rights reserved.