IPA web run node and IFS

We recently migrated from Mingle 11 to Infor OS CE. Since we are on v10 and have users in LSF and Landmark, it's understood that disabling of user accounts for terminated employees is best done via IFS so that the ION BODS can then disable in both LSF and Landmark. Is there a way to use an IPA web run node to conduct this disabling in IFS? I can't find any find any documentation on this and experimenting with what I've gathered from the browser's developer tools during a post action has not produced any success.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

unknown

Are you familiar with the ION API application in InforOS? There are a suite of IFS related web services available in ION API. ION API web services are authenticated with OAuth2 (which can be mimicked using the web run node in IPA). So I could see a way to call IFS from IPA via ION API web services to disable a user.

The other possibility is that User BODs are bi-directional. If your system is setup to send changes from Landmark, you could disable the Actor in Landmark using a Landmark transaction node in IPA. That would trigger a "Process" BOD from Landmark to IFS.

brian-dittman

Thanks for that. I did peruse the ION APIs for IFS services but did not see anything that would disable a user. The bi-directionality of the BODS is actually something I had originally planned to capitalize, but it seems that disabling a user in Landmark will not disable in IFS by design. Infor's documentation indicates this is so because there are many Infor apps, so disabling in a downstream app should not cut off access upstream. I also posed my inquiry to Infor support, so if I get a working solution from them, I'll update here to share the details.

unknown

My guess is that the PATCH web service call in IFS could be used to update the Active flag, but I can't figure out the syntax of the JSON body. Are you familiar with SCIM? If you enable SCIM, you could use the SCIM URLs to update and make them inactive.

SCIM uses Basic Auth, so you could easily make that call via a Web Run in IPA.

The URL will look like this:

mingle-scim.inforcloudsuite.com/TENANT_NAME/v2/Users/b88243b6-70d1-4cde-987b-d6e5e9ac459a

Where "b88243b6-70d1-4cde-987b-d6e5e9ac459a" is the UID of the IFS User

The Body would be JSON like this:

{

"schemas": [

"urn:ietf:params:scim:schemas:core:2.0:User",

"urn:params:scim:schemas:extension:infor:2.0:User"

"userName": "user@client.com,

"name": {

"familyName": "Doe",

"givenName": "Jane"

"displayName": "Jane Doe",

"emails": [

{

"value": "user@clientcom",

"type": "work",

"primary": true

}

"title": "User",

"preferredLanguage": "en-US",

"locale": "en-US",

"timezone": "America/New_York",

"active": false

}

unknown

web program is: ...../v2/Users/<!IFSUserId>

Post string is:

{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
"Operations": [{
"op": "replace",
"value": {
"active": false
}
}]

Copyright © 2025 Infor. All rights reserved.