SAP BTP workflows principal propagation to on-premise SAP

[enric101]

Hi gurus,

I have a requirement that we need to sent a confirmation from a workflow to SAP ECC system. We have configured principal propagation to SAP BTP using cloud connector an it runs for a SAP Fiori applications deployed in SAP BTP connected in SAP ECC on-prem.

But when I activate in the workflow the flag "principal propagation" and user a destination with type principal propagations, the workflow return an error that say "Principal propagation type is not permitted"

I checked the documentation but I don't see any relevant information about this scenario.

Could you help me about an approach to use principal propagation to our backend in SAP BTP workflows?

[Srinivas-Rao]

Hi - I am also learning SAP workflow management, so I may be wrong but have you checked this:

https://help.sap.com/viewer/e157c391253b4ecd93647bf232d18a83/Cloud/en-US/e8b9b990bf69416d910ed7d2651...

Anyway, I am following the thread to see the correct resolution.

Thanks & Regards

Srinivas Rao.

[enric101]

Hi Srinivas,

Thanks but I checked and the problem persist. The problem is related with a destination with principal propagation type, this is the message: "The authentication type 'PrincipalPropagation' is not supported. For supported authentication types, see the Destinations section in the SAP Workflow service documentation."

In the following URL exist the documentation about on-premise connections but just only using basic authentication:

https://help.sap.com/viewer/e157c391253b4ecd93647bf232d18a83/Cloud/en-US/c4eeb034167e4879b2e3cf86f63...

Regards

Enric

[Archana]

Hello Enric,

Thanks for the solution provided above.

• Principal Propagation is not supported inWorkflow for On-Premise via Cloud Connector. Here is the troubleshooting. You can try using Basic Auth instead (as described here).

[enric101]

Hi archana.shukla ,

I try to call a microservice to check the principal propagation but now we have this error:

We tracked the calls using API management but it seems that the call It does not even reach the destinations service.

Regards

Enric

[enric101]

After some investications I concluded that the problem could be solved with the approach on this blog:

https://blogs.sap.com/2020/10/10/sap-apim-route-service-plan-to-manage-cloud-foundry-apps/

Or using SAML assertion

https://www.youtube.com/watch?v=LFDtvSNCtr4&ab_channel=SAPHANAAcademy