Why the & (escape character) is parsed as & in OSB Pipeline Assign/Replace Actions? (Doc ID 3043171.1)

Last updated on SEPTEMBER 23, 2024

Applies to:

Symptoms

 When in an OSB Service Account Resource is stored in the password field a & character (escape character) if this is used in a Pipeline (Assign/Replace) as an XML document, this is parsed as &

For example the Service Account resource "MyServiceAccount" in a ServiceAccount Folder inside the OSB Project has:

User Name: myuser
Password: te&m

If in the OSB Pipeline you have: (OSB Project Name = MyOSBProject)

Assign fn-bea:lookupBasicCredentials('MyOSBProject/ServiceAccount/MyServiceAccount') to variable test

Assign
<sas:NewDocument xmlns:sas="http://tempuri.org/">
<username>{$test//*:username/text()}</username>
<password>{$test//*:password/text()}</password>
</sas:NewDocument>

to variable NewVarXml

Replace Action
Replace <XPath> in variable body with $NewVarXml
Replace node contents
-> Save

If you test this the result will be:

<sas:NewDocument xmlns:sas="http://tempuri.org/">
<username>FilnetAQEnv</username>
<password>te&amp;m</password> <============ Here & escape character was parsed as &amp;
</sas:NewDocument>

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.