This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 30%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVT%3C/text%3E%3C/svg%3E)
I have custom policy which calls legacy IDP through REST API and I am seeing following results:
Scenario 1:
Response from API
{
"tokenSuccess": True,
"migrationRequired": False
}
result on b2c policy : Error message : The claim exchange <Id> specified in step <order> returned HTTP error response that cannot be parsed.
Scenario 2:
Response from API
{
"tokenSuccess": true,
"migrationRequired": false
}
result on b2c policy : Success works as expected.
Is data type using in custom policy (Boolean) case sensitive? Is there any way to work scenario1 using custom policy?
Hi @Vikas Tiwari , are you following any documents for this? I always treat custom policy data as case sensitive. There may be a way to get scenario 1 to work but may I ask why you need it to be uppercase? I assume it has something to do with the legacy IDP?
We can change api to lower case I was curious to know if there is anyway to control custom policies to handle upper case as well.
Hi @Vikas Tiwari , unfortunately we do not offer the option to handle uppercase. I would suggest submitting a feature request here.
If this answer helped you please mark it as "Verified" so other users may reference it.
Thank you,
James