Skip to main content
Question

Issue with FSM- PPM Integration After SSO Implementation

  • November 19, 2025
  • 3 replies
  • 18 views
A
Sidekick (Partner)
Forum|alt.badge.img+6

We have Recently implemented SSO on our PPM development instance. As part of the process, non-federated user accounts now require email-formatted usernames.
We have an FSM integration that updates certain data in PPM (e.g., task dates and status). After SSO changes, FSM is failing to send updates because the credentials used in the XML scripts for integration still reference the old username format.

Could you please suggest, what is the recommended approach to update FSM integration credentials and test them before moving SSO changes to production?

Advance thank you!!

 

 

3 replies

roklde
Superhero (Employee)
Forum|alt.badge.img+27
  • roklde
  • Superhero (Employee)
  • November 19, 2025

Hi Aishwarya,

did you setup OIDC only in the FSM_AUTHENTICATION_METHODS app param? If you are depended to  still use user/password combination you may use FSM, OIDC as the value for that parameter.

Further, since FSM6U25 support for “Headless” Authentication (OAUTH2) is available for Odata to support integrations. This mechanism is limited to a single message user and works only with Azure AD. See the attached FSM6 OData APIs Guide for information on configuring this.

Best regards
Roman

1 Attachments
A
Sidekick (Partner)
Forum|alt.badge.img+6
  • aishwarya
  • Author
  • Sidekick (Partner)
  • November 20, 2025

Hi Aishwarya,

did you setup OIDC only in the FSM_AUTHENTICATION_METHODS app param? If you are depended to  still use user/password combination you may use FSM, OIDC as the value for that parameter.

Further, since FSM6U25 support for “Headless” Authentication (OAUTH2) is available for Odata to support integrations. This mechanism is limited to a single message user and works only with Azure AD. See the attached FSM6 OData APIs Guide for information on configuring this.

Best regards
Roman

Hi ​@roklde 

Thank you for your response

Currently, our FSM_AUTHENTICATION_METHOD parameter is set to FSM, so only FSM username/password authentication is enabled.

A
Sidekick (Partner)
Forum|alt.badge.img+6
  • aishwarya
  • Author
  • Sidekick (Partner)
  • November 24, 2025

Hi Team,

We have reviewed the Message Routing Rules, XML Maps, Integration Functions, and the Integration Log.

Below finds the integration log message:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><obj:Auth xmlns:obj="http://www.niku.com/xog/Object"><obj:Username>fsm_integration</obj:Username><obj:Password>aaYRJZ4RngNY8W</obj:Password></obj:Auth></soapenv:Header><soapenv:Body><obj:WriteCustomObjectInstance xmlns:obj="http://www.niku.com/xog/Object"><NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd"><Header action="write" externalSource="NIKU" objectType="customObjectInstance" version="15.8.0.260"><args name="overrideAutoNumbering" value="false" /></Header><customObjectInstances objectCode="znecinboundtask"><instance instanceCode="" objectCode="znecinboundtask"><CustomInformation><ColumnValue name="partition_code">NIKU.ROOT</ColumnValue><ColumnValue name="page_layout">odf.znecinboundtaskFrame</ColumnValue><ColumnValue name="name">PPMFSM</ColumnValue><ColumnValue name="code">-1</ColumnValue></CustomInformation></instance></customObjectInstances></NikuDataBus></obj:WriteCustomObjectInstance></soapenv:Body></soapenv:Envelope>

 

Please find attached the screenshots of the Message Routing Rule, one XML Map, and an XML Function for your reference.

Please let me know if any additional details needed.

 

Thanks In Advance!!

7 Attachments
Grzegorz Byrski
Terms & ConditionsCookie settingsAccessibility statement