Are you flowing the original user credentials through BizTalk and into Oracle? That is the problem that SSO is designed to solve. You just mentioned that you have to re-enter the password every time you promote the application, and there is a simpler solution than SSO for that problem. To keep from re-entering the password every time you promote the app, just open the binding file in a text editor and do a find and replace of “Password=**********” with “Password=<real password>”.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name