Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Currently I am using the structure <EncryptedData..<EncryptedKey>...</EncryptedKey>...<CipherData>...</CipherData>..</EncryptedData> in the SOAP API for interacting with dynamics crm SOAP URI. (POST <Execute.. request)
Now since WS-TRUST authentication is going to deprecate, and only OAuth authentication is there which return bearer key. Can some one help me how we can use Bearer token with soap body?or is there any other authentication from which we can get <EncryptedData..<EncryptedKey>. ?
I'm not sure if I totally understand your question but it seems that you already have access to a bearer token, and you want to use it in a SOAP request, if so:
1. Add a REST request of the POST type.2. Add the OAuth Authorization for the request: https://support.smartbear.com/readyapi/docs/projects/requests/auth/profile/request.html3. Select the application/xml Media Type in the Content Editor: https://support.smartbear.com/readyapi/docs/projects/ui/request/request/vertical/rest.html4. Add your SOAP request XML as the payload.As a result, you will get a request with the OAuth access token and the SOAP request content:
In the soap request body, what should be the tag name for Oauth access token instead of this structure
<o:Security xmlns:o="docs.oasis-open.org/.../oasis-200401-wss-wssecurity-secext-1.0.xsd"><u:Timestamp u:Id="_0">
Also, if I am adding it in the Authorization HTTP header of a request, then receiving this error - An error occurred when verifying security for the message<500 Internal Server Error>
Hello. Did you solve that issue?
I am facing the same issue. I have the authorization token, I am also getting "An error occurred when verifying security for the message". Were you able to solve this issue?
Is there any update on this issue? I could really use some help.
I couldn't find any solution, how to use OAuth with SOAP. So I had to rewrite the whole application to their new Web API (docs.microsoft.com/.../query-data-web-api). It took me a lot of time, but I think, it is the only solution right now. It is really inconvinient, that they are deprecated that authorization out of nowhere and didn't provided a reasonable solution.
There is one hack to do that. You can remove the secure body from the soap body and add pass bearer key as a Authorization header.
For that you need to convert your soap body to soap 1.1. (namespace should be "schemas.xmlsoap.org/.../")
Hi Abdul , can you please expand on how to change the request to SOAP 1.1. Did this solution worked for you to get around WS-trust deprecation.
Hi Tiago, I as suggested in the example i have sent the soap envelop as Post request body and authorization code and soap action in the header. I can see a response from MSdynamcis server as key for the created record. But when i don't see the record in MSDynamcis portal under "Lead" category. Any pointer on what could be the issue.
Business Applications communities