Mingle -> InforOS experience

 2 Replies
 1 Subscribed to this topic
 121 Subscribed to this forum
Sort:
Author
Messages
Any ideas?
Basic Member
Posts: 20
Basic Member

    We have accepted the risk of not doing the "mingle -> inforos" install because we are in the middle of workday implementaion. I was asked to task the effort/time/money required take up this work if this cant be avoided in future.

    A year ago, we have also went through an excercise of upgrading our LSF, Landmark(from 10 to 11) and inforos install by ourselves in one of our test environment but the issue we ran into was we were not able to setup LS as STS within Infor OS. We were told that we would need additional licensing for this and we were also told that this can be only done by Infor or their partners for extra cost. Is that still the case?

    One other thought we had was, to NOT expose Infor OS URL to the users but only the LSF URL (we will still keep the Infor OS in our stack just in case if we were to reach out to Infor for Support). When you access InforOS (without the LS as STS) - it asks you to authenticate twice, one for InforOS and another LSF. Do you guys see any other risk with this approach?

    We are currently bind to ldap. Do you guys see any foreseeing risk of us not doing this upgrade for next year or so and lose the ability to apply year end patches within Lawson S3? By the same time next year we will be in workday.

    Brian Allen
    Veteran Member
    Posts: 104
    Veteran Member
      I'm not able to speak to on-premise requirements, but we're implementing CloudSuite and it was an easy change to move the Infor OS Portal since Infor managed the backend process. It was made available to all MT customers a couple of months ago and we only needed to add a /v2/ in the URL to access it. We previewed it on our environments and I had them make it our default as of this week. It's a great Portal with significantly more capability than Mingle. We go live with HR Talent / GHR in a couple of weeks and I've tested using a direct link to Employee Space, bypassing the OS Portal for that audience and it works fine.

      It's difficult to say if you would run into an issue with patching - Infor may be able to comment. Infor will move all MT customers to it as default in April, 2024 and stop supporting Mingle. If I were in your position, I would have a consulting parter like Intellias or others to activate it for you if you think you may have to do any patching.
      Jimmy Chiu
      Veteran Member
      Posts: 641
      Veteran Member
        Let's start with Infor stopped supporting LS as STS authentication back in March 1, 2019. So you went thru couple years of YE patching without issue already! ADFS/Infor OS as STS are the two supported authentication method.

        As of Mingle/Infor OS, it's just a wrapper. It has nothing to do with any lawson forms processing within LSF. YE patches do have a minimal LSF environment version stated. So you may want to check the requirements.