Error when try to use Docusign app in Salesforce1 - salesforce

I'm trying to use Docusign by Salesforce1, and when click on the Docusign button is occurring an error:
Error Domain=DSAPIManager Code=1004
"One or both of Username and Password are invalid."
UserInfo={
DS_API_MANAGER_ERRO_ID_KEY=USER_AUTHENTICATION_FAILED,
NSLocalizedDescription=One or Both of Username and Password are invalid.,
RKObjectMapperErrorObjectsKey=(
"[DSAPIErrorResponse{
message= One or both of Username or Password are invalid.;
errorCode=USER_AUTHENTICATION_FAILED; error = (null);
}]
")
}
This is occuring in a mobile IPhone and for not for all users.
In debug log doesn't appearing anything and in the Docusign log too.
We are appointing the correct Docusign URL (NA2,NA3).
The steps that the user are doing is:
Log-in into Docusign app > authenticate with user and password> after logged he goes to the Salesforce1 > select an opportunity > click on Docusign button > select a document and a recipient > click on Docusign button.
After this process the error occurs.
Could someone help me?
Thanks
Rafael

When you login to the DocuSign Mobile app they login to one user - but your Salesforce Org actually has them synced with another user.
Or your user has some recipient accounts that need to be closed probably a Force User Sync after in DocuSign eSignature for Salesforce.
The steps that the user are doing is: Log-in into Docusign app > authenticate with user and password> after logged he goes to the Salesforce1 > select an opportunity > click on Docusign button > select a document and a recipient > click on Docusign button. After this process the error occurs.
You would also need to make sure they choose the right server/environment for that first step.

Related

Azure B2C using password reset userflow token is getting expired and not able to login into application home page

User is landed into Reset password screen.
User configured his application password through Azure B2C reset password userflow.
Application page is redirected and user is again asked to provide credentials
Our requirement is - User should land into the Application Dashboard/Home page directly after password is reset through reset password userflow.
I reproduce the issue and it is working fine for me. Please use the below setup for creating Password Reset UserFlow as I have done.
Step 1: Selected “Reset Password using email address” under local account.
Step 2: Did Application claim.
Step 3: Gave access token and id token for authentication for the application.
I have recorded my output in this GIF. Please check out this.

Docusign eSignature - This User lacks sufficient permissions

I am trying to setup the Docusign eSignature i nSFDC, through the Docusign APP Launcher and I am getting this error message whenever trying to create an Envelope template : "You are not authorized to access the envelope."
With the following API status in my Docusign API dashboard : ERROR: This User lacks sufficient permissions. :: Setting: userOverrideEnabled.
[.
Does anyone know what could be reason ?
Few more details :
I've seen in a post from Docusign that the error could come from having "Allow sender to download form data" unchecked. But it did not change anything in my case.
I'm admin in SFDC, in the Docusign App launcher in SFDC & the user who activated the integration. My email address is not registered as an Admin user in Docusign (im logging as some one else who is the admin in Docusign)
Best,
Lucas
To fix this issue your user has to be admin in DocuSign also.

Is there a way to keep user logged in to Azure ADB2C when they attempt to link a social account and click cancel?

When someone goes to link their social media account to their ADB2C registration, we have a problem whereby we are unable to distinguish between a failed ADB2C sign in, and the cancellation of their request to link their social media account.
When someone, for example, tries to link their Facebook account, a URL like this sits behind the 'Not now' link:
https://test.b2clogin.com/test.onmicrosoft.com/oauth2/authresp?error=access_denied&error_code=200&error_description=Permissions+error&error_reason=user_denied&state=StateProperties%3DeyJTSUQiOiJ4LW1zLWNwaW0tcmM6NzMyYWQzZWXtZGI4OS00YjZiLTlmYzgtYTY5NzYxZDdjMDY0IiwiVElEIjoiNTcxZWE5M2UtODQ4NS00MTMzLTlhZmItOTQwMWIyMDAwOGE5IiwiVE9JRCI6Ijc4ZDUxNTY3LTkzYTAtNDEyMy1iMHI1LTVmN2E1NzNjMzRkYSJ9#_=_
We trap the AuthenticationFailedNotification, but within it, we haven't been able to find a way to distinguish between
an access denied message based on the cancellation of the request to link a social media account, and
an actual genuine access denied response.
We check:
if (notification.ProtocolMessage.Error == "access_denied" && notification.ProtocolMessage.ErrorDescription.StartsWith("[A SPECIFIC ERROR ID]", StringComparison.InvariantCultureIgnoreCase))
We would then have a specific user flow configured for each scenario, based on the error description, authentication policy and authentication type (social media or ADB2C).
Our requirement is for the user to remain logged in to ADB2C when they attempt to link a social account, but don't actually go through with it.
Microsoft's own example, https://woodgrovedemo.com/ works in the same way, whereby the user is logged out when they cancel the linking of their social media account (for example, by clicking 'Not now' when going to link their Facebook account).
You can't, because it's the same thing!
When a user cancel the Facebook process with the 'Not now' button, the user ain't logged in. You need the user to accept to be link to your app for Facebook to send an approbation and a claims to be delivered to your app. Without this claims, the user is not logged in.
So you can't have a requirement to keep the user logged in, since he haven't been logged in yet. It's false to think that the Microsoft's example logged out the user, since he was never logged in.

Azure AD B2C : Back option to previous orchestration step in user journey

I have a requirement to give option to user to edit the details he has given in previous steps.
Example:
OrchestrationStep 1: Collect user info like name, email, country
OrchestrationStep 2: Send email verification and verify the email. Here there should be an option change his details like email. When user click on that link, we should show step 1. Else continue to Step 3.
OrchestrationStep 3: Collect other details like password.
How to implement this?
In the B2C, the user sign-up flow follows this steps for the local account with email:
Verify the email by sending the code
Set password
Collect user info like name, email, country
Note: If you enable MFA, when you click create, it will redirect to the MFA page to verify the user.

Powerforms submit - getting Docusign Envelope ID

We are incorporating Powerforms into a Salesforce Community. When a user completes a Powerform, we need to execute a trigger to write back to Salesforce.
My questions are related to attaching the completed Docusign envelope to the related Salesforce record:
1) When we redirect from Powerforms, will we get the Docusign envelope ID?
2) If so, can we insert a Docusign envelope record in Salesforce with that ID with the standard AppExchange package to tie the envelope to the record in Salesforce from which the Powerform was initiated?
Any thoughts would be much appreciated.
Thanks,
Mike
If you're logged into DocuSign: Go To Admin>> Signing Settings>> In-Session Landing Pages
In-Session Landing Pages is used by Powerform to redirect the signer to the URL where you want Signer to redirects to. When Signer gets redirected then DocuSign populates URL like below:
{RedirectUrl}/?env={envelopeId}&pf={powerformId}&r={recipientId}
Alternatively and also recommended is to use DocuSign Connect, where you subscribe for the event like Envelope Completed or Recipient Signed etc, once event occurs then DocuSign will push an XML message to your configured listener with the envelope related details. This is a better approach because with redirect there is a risk of the customer closing the browser or browser getting crashed before browser hits your app URL.

Resources