Account
Earned badges
Achievement: Latest Unlocked
Replies
Topics Started
Preferences
Topic Started
Topics |
---|
We have registered Callback Event Notification on OneSpan Sign Web UI and Key is getting gernerated correctly. |
We're trying to generate the package using template. Templates are created in sandbox.esignlive.com. |
Replies Created
Reply to: OneSpan SDK to retrieve
Wednesday, February 28, 2024 at 04:57pmHi Duo, Thank you for sharing the Role ID but how I can get it dynamically as we are dealing with 18 different templates?
Reply to: Unauthorized 401 error for CallBack Failure
Thursday, March 7, 2024 at 05:44amHi Duo,
We have modified OneSpanAPIObjects class to change the Origin from Salesforce to OSS but for the first point that you mentioned when we are utilizing POST /api/callback with below payload:
Please note that we have generated Base64 Encoded Key using:
String inputString = '{"host": "test.salesforce.com","client_id": "3MxxxxY9.g==","refresh_token": "5AexxxxxxoK"}';
Blob binaryData = Blob.valueOf(inputString);
String base64String = EncodingUtil.base64Encode(binaryData);
system.debug('Base 64 - '+base64String);
{
"url": "https://xxxx.sandbox.my.salesforce.com/services/apexrest/OSS/callback",
"events": ["DOCUMENT_SIGNED","EMAIL_BOUNCE","KBA_FAILURE","PACKAGE_ACTIVATE","PACKAGE_ARCHIVE","PACKAGE_ATTACHMENT","PACKAGE_COMPLETE","PACKAGE_CREATE","PACKAGE_DEACTIVATE","PACKAGE_DECLINE","PACKAGE_DELETE","PACKAGE_EXPIRE","PACKAGE_OPT_OUT","PACKAGE_READY_FOR_COMPLETE","PACKAGE_RESTORE","PACKAGE_TRASH","ROLE_REASSIGN","SIGNER_COMPLETE","SIGNER_LOCKED","TEMPLATE_CREATE"],
"key": "eyJxxxxyJ9"
}
It registered successfully and added it on UI but we are still facing below error for each event notification:
URL:
Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_CREATE","sessionUser":"U5HU2N7UHN8U","packageId":"2ZpiA7uVoxVWnn0XgEdfzLQpqDM=","message":null,"documentId":null,"createdDate":"2024-03-07T11:39:57.402Z"}
Reason(s): status code: 401, reason phrase: 401: Unauthorized
URL:
Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_ACTIVATE","sessionUser":"U5HU2N7UHN8U","packageId":"2ZpiA7uVoxVWnn0XgEdfzLQpqDM=","message":null,"documentId":null,"createdDate":"2024-03-07T11:39:59.280Z"}
Reason(s): status code: 401, reason phrase: 401: Unauthorized
Thanks,
Ankit
Reply to: Unauthorized 401 error for CallBack Failure
Thursday, March 7, 2024 at 04:00pmHi Duo,
I guess it is US2 Sandbox and email address is correct. I didn't check your response and hit the POST /api/callback one more time. This has added Callback URL and Key once again.
We have enabled the debug log and cleared the Callback URL and Key from UI. If you have enabled the callback connector for our account then how our rest API endpoint can listen to the callback events.
As event notification on Sandbox Integration UI is reset now. How would we test it if it works?
Thanks,
Ankit
Reply to: Unauthorized 401 error for CallBack Failure
Friday, March 8, 2024 at 10:14amHi Duo,
We have used API Endpoint methodGET /api/callback/connectors/salesforceOauth2 and it worked fine. Also enabled the debug log for Callback listener apex class and it worked.
Where did you enable for callback connector for our account?
Thanks,
Ankit
Reply to: Unauthorized 401 error for CallBack Failure
Thursday, March 21, 2024 at 03:42pmHi Duo,
Thank you, all of your suggestion helped us to work in different Sandboxes. We went live yesterday, could you please help us to register the Callback for US1 PROD for [email protected] account?
Also, we registered callback in multiple sandboxes using Onespan Swagger - OneSpan Sign Sandbox | OneSpan Community Platform. How I can register it for Production environment?
Thanks,
Ankit
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
We have registered Callback Event Notification on OneSpan Sign Web UI and Key is getting gernerated correctly. |
11 | 1 month ago | 94 | |
We're trying to generate the package using template. Templates are created in sandbox.esignlive.com. |
3 | 1 month 4 weeks ago | 34 |