Error Messages: When I am trying to connect DocuSign with salesforce, I am getting error "Web service callout failed: Unable to parse callout response. Apex type not found for element turnTLSv11Off"
Install DocuSign for Salesforce from App Exchange
Go to DocuSign Admin tab
Connect DocuSign demo account. It will get connected successfully.
Connect DocuSign with Salesforce . Enter Salesforce username and credentials
Error messages : Web service callout failed: Unable to parse callout response. Apex type not found for element turnTLSv11Off
This is a known issue that is being investigated. The current workaround is to configure SF Admin credentials in Connect (Log in to the DocuSign Web Console > Settings > Connect > Salesforce > Reconfigure login). As the previous step is completed, that'll get things linked from both sides.
Related
Have tried many ways via code and Postman and no luck of getting a state of subscription like you would get via this link: https://learn.microsoft.com/en-us/rest/api/resources/subscriptions/list - here via the site you get a list of subscriptions and their "state": "Enabled" as an example.
Have no problem of getting auth tokens using scopes below but then impossible to get subscriptions list. If I use token from Microsoft site, the call in Postman to get subscriptions works fine.
The site is using Azure Active Directory OAuth2:
Type: oauth2
Flow: implicit
Authorization URL: https://login.microsoftonline.com/common/oauth2/authorize
Using Postman I have tried getting subscriptions using these scopes along with auth token:
api://blah/.default - Invalid Authentication Token Audience
https://graph.microsoft.com/.default - Authentication failed
https://management.azure.com/.default - pass but 0 results
https://management.core.windows.net/.default - pass but 0 results
I guess when using the site you login as a user and password vs in the code using client app and app secret. Is this workflow even possible?
The registered app has all kinds of API permissions. Something this simple should not be so hard. The idea here is to programmatically check via console app if Subscription is "Enabled".
After debugging this via Postman it turns out to be a permissions issue where you have to add the application you created/using to authenticate to the Access Control (IAM) of the subscription. This post describes the error and resolution: The client with object id does not have authorization to perform action 'Microsoft.DataFactory/datafactories/datapipelines/read' over scope
If you have multiple capacities created then you have to add your application to all of those subscriptions. Then you will get a list and can then check each one.
I am following instructions provided by Microsoft to set up Postman for testing an Azure AD B2C secured Wep API:
https://learn.microsoft.com/en-us/aspnet/core/security/authentication/azure-ad-b2c-webapi?view=aspnetcore-3.0
https://learn.microsoft.com/en-us/azure/active-directory-b2c/tutorial-register-applications?tabs=applications#register-a-web-application
Under the section Use Postman to get a token and test the API, I get to Step 4 where the documentation states:
Postman opens a new window containing the Azure AD B2C tenant's
sign-in dialog. Sign in with an existing account (if one was created
testing the policies) or select Sign up now to create a new account.
The Forgot your password? link is used to reset a forgotten password.
This does not happen.
I am using the Implicit Grant Type and my Auth URL appears as follows:
https://<myDomain>.b2clogin.com/<myDomain>.onmicrosoft.com/oauth2/v2.0/authorize?p=B2C_1_SIGNUP_SIGNIN&client_id=d4d84f32-1e57-4daf-b010-399bb2614e0d&nonce=defaultNonce&redirect_uri=https%3A%2F%2Fjwt.ms&scope=openid&response_type=id_token&prompt=login
Scope is set to the following value:
https://<myDomain>.onmicrosoft.com/postman/user_impersonation openid offline_access
When I press the Postman Request Token button, the SignIn / SignUp User Flow (Policy) is interrupted with the following Error dialog stating:
Sorry, but we're having trouble signing you in. We track these errors
automatically, but if the problem persists feel free to contact us. In
the meantime, please try again.
Correlation ID: c1b01e2d-84ce-446e-a9c2-f3a8617eb9f2
Timestamp: 2019-11-21 20:03:31Z
AADB2C90018: The client id 'd4d84f32-1e57-4daf-b010-399bb2614e0d,d4d84f32-1e57-4daf-b010-399bb2614e0d' specified in the request is not registered in tenant '<myDomain>.onmicrosoft.com'.
Taking this client ID is not registered error on face value, the problem would appear related to improper registration of the Application (Client) within Azure AD B2C.
However, I am able to successfully run this SignIn / SignUp User Flow from within Azure AD B2C; and to successfully register new Users using that Policy.
To be clear, my ASP.Net Core Web API is not being run at this stage. I am simply trying to configure Postman to request a New Access Token from Azure AD B2C.
I have tested the document you provided and it works fine for me.
Based on your error message, it seems that you put your client id twice in the Client ID.
AADB2C90018: The client id
'd4d84f32-1e57-4daf-b010-399bb2614e0d,d4d84f32-1e57-4daf-b010-399bb2614e0d'
specified in the request is not registered in tenant
'.onmicrosoft.com'.
Please check it.
On docusign admin console, I was able to setup docusign recipient authentication using access-code, SMS and phone.
While trying for SAML, I received error message:
"Your envelope is incomplete. Recipient XXXX does not have SAML authentication setup adequately (missing assertion attribute values)".
Please share any information pertaining to how we may overcome this error message.
This is no longer a supported feature for DocuSign. If wanting to use SAML, you must purchase SSO. Here is the latest implementation guide: https://support.docusign.com/en/guides/single-sign-on-implementation-guide
Hi: I have a Dynamic CRM server set up on an Azure VM. I configured the web address for the CRM to be accessible from outside the VM. When I log in via a browser I'm prompted for credentials to the VM and then everything connects fine. When I try to connect via Outlook I am not prompted for a user/pwd and the connection attempt errors out with the following message
"The caller was not authenticated by the service. ---> System.ServiceModel.FaultException: The request for security token could not be satisfied because authentication failed."
Any help to the problem would be much appreciated!
Dynamics CRM hosted in Azure is not a supported configuration, this is probably the cause why the outlook client is not able to connect.
In the Developer Portal of Azure Api Management, having selected an API and an endpoint, im getting the following error when authorizing using OAuth:
An error has occurred while authorizing access via Identity (AD):
invalid_request ACS50001: The required field 'resource' is missing.
Im logged in with an administrator account and all the relevant "products" associated.
Any help is most appreciated.
“Resource” is a required parameter for AAD. That should be your APP ID. It must be entered in the “additional request body parameters section” on the OAuth settings page.