Hi Team,
Did you find anything on this?
I’m waiting for the plugin developer’s response regarding some things. Once I have more information, I will be in touch with you.
We recently updated the getJWT() method to increase the default timeout from 10 seconds to 30 seconds. However, we are still encountering the issue.
Upon reviewing the logs, we identified the following root cause:
ASPOSE Service Exception: System.CalloutException: Unable to tunnel through proxy. Proxy returns “HTTP/1.1 503 Service Unavailable”
Do we need to increase the time or there any other option to fix? if this required increase time what will be the time ?
In version 1.1 we are doing encoding. Sample code:
image.png (15.7 KB)
Should we encode same in V4 as base64?
No, I don’t think that timeout is the reason. I’m in the process of creating my own sales force app and will try the debug plugin directly from Salesforce.
Speaking of encoding - no, you shouldn’t do that, and if you use the code you shared with me for
String client_id= credentials.appSID;
String client_secret= credentials.appKey;
HttpRequest request = new HttpRequest();
request.setEndpoint(credentials.accessToken);
request.setMethod('POST');
request.setHeader('Content-Type', 'application/x-www-form-urlencoded');
request.setHeader('Accept', 'application/json');
String body = 'grant_type=' + grant_type + '&client_id=' + client_id + '&client_secret='+ client_secret ;
request.setBody(body);
request.setTimeout(20000);
Http http = new Http();
HttpResponse res = http.send(request);
String jsonInput = res.getBody();
it should be enough
@yaroslaw.ekimov we have shared all the code that is used in our implementation. Let us know at your earliest what you find so we can update our Leadership.
Sure, I will contact you as soon as i have any updates
Any update on this request?
I’m trying to reproduce it in sales force but for now I can’t replicate that issue. I will spend some more time to do this if nothing help I will raise a new issue to upgrade or even create a new plugin for sales force.
Thanks for the update.
I couldn’t reproduce that connection issue. So for now I can’t share any ETA when it will be fixed as it really hard to reproduce. We have planned to implement a new plugin that can fix that issue, but still now I don’t have enough information to share ETA.
Can you provide more information on the plugin you have described here to fix the issue? do we need to update the API as well
We planned to release a new version of the Apex plugin for Salesforce. We will try to make it easier to debug if something is wrong and easier to use(here, I mean less code from your side to execute the same operation).
Hello,
Any update on this?
No, when there is any update, I will contact you. We have planned some testing for that week, after that, it will be clearer about ETA.
Hi,
Do we have any further update on this?
Part of a new plugin was developed, when it’s finished we will publish it and I share the link with you.
1 Like
Is this change is an API which we can take and configure it like aspose 4.0? or we need to do a code change to take new changes?
It will be a new plugin for Salesforce, so there will be a code change
Can you provide us what changes we can expect to make on our code base so we can start ahead to take the new plugin?