ION errors: Error executing IDO request for BOD Sync.SecurityUserMaster. This SqlTransaction has com

Hi,

I have added "Sync.SecurityPermissionMaster" to Factory Track connection point in ION expecting security roles changes to go from mingle to FKT.

However now I get errors in ION like this:

Error executing IDO request for BOD Sync.SecurityUserMaster, site COMPANYNAME_TRN_COMPANYNAME: This SqlTransaction has completed; it is no longer usable.

Any ideas why this error happening and how to get mingle roles to migrate to FTK?

Thanks

Kirill

Find more posts tagged with

Accepted answers

All comments

Kevin Heiman

I can't answer why the error, but give a perspective on User and security patterns. I am not a Mongoose developer, but have worked with scenarios around Mongoose security patterns.

Security Roles are defined and owned by the application endpoint. Users are defined and maintained by IFS.

Entitlements to users are via Roles which are granted in IFS. As IFS is the SoR for users it will sync any changed to the user out to ION defined subscribers.

Securrty Permission Master is to be used by the Application endpoint to publish fine grained authorities to an application that is interested in collecting those. As an example, Infor Global Risk and Compliance (GRC) uses this data.

Mongoose should be set to publish any roles and role changes to IFS using Sync.SecurityRoleMaster. While you can create Roles in IFS, you cannot assign a LID to represent any application in the network. This is a special use case need. All roles should be in the application as the SoR of that application, and published to IFS.

Mongoose should only consume User Master and make changes to its user repository. Mongoose changes to users should not be published as a SecurityUser Master.

So I think the answer to your need is that you want to manage Application roles in the application, which are then sent to IFS. They can then be applied to users, which will send the user to the application with thier roles and other details.

I don't think you want the UserPermissionMaster in this scenario. Hopefully that was helpful...

(Nov 1 - I noticed the image i prepared was missing... adding)

Kirill Kuchumov

Thanks Kevin.

It's a very detailed reply!

Kevin Heiman

I updated the prior response with an image that was missing, and some cosmetic wording and spelling corrections..

Also note that if you change these patterns in ION, you need to also make the changes in Mongoose. This is primarily around turning off a message, as Mongoose will still publish it unless you go into the BOD configurations and turn off publishing for those affected messages. Otherwise the messages will stack up in the outbox and grow, or cause no route messages in ION desk. Note that IO Box is moving to using API based IMS soon.

For messages coming into Mongoose, if you add a new ION pattern, then you need to account for that as well.

My observation has been this is mostly aobut Mongoose publishing patterns, turning off Security User master outbound. But I am a not the Mongoose technician to go much deeper.

Copyright © 2025 Infor. All rights reserved.