No documentation about AppSecret Proof for Server API calls? - facebook-graph-api

If I enable the option giving in Advanced Settings is gives me BAD Request or error code 400
If I enable this option, what is the required value of AppSecret_Proof parameter?

If you visit github and have a look at their PHP SDK's code, you'll find how they generate appsecret_proof's value.
This part was recently added so you have to refer to the latest version of PHP SDK. To activate/inactivate, as you already know, you have to visit App Dashboard > Setting > Advanced.
EDIT: 2013-08-09
Now they have official document.

From the documentation article Securing Graph API Requests:
The app secret proof is a sha256 hash of your access token, using the app secret as the key. Here's what the call looks like in PHP:
$appsecret_proof = hash_hmac('sha256', $access_token, $app_secret);

Related

Unable to use any of the API of Zephyr Scale Server API (v1). Showing 404 Status / Dead Link issue

I am trying to use APIs from this https://support.smartbear.com/zephyr-scale-server/api-docs/v1/ documentation, where I am Unable to get the response. I am fulfilling all the specified requirements as mentioned in above documentation.
http://{My_Jira_URL}/jira/rest/atm/1.0/testcase/{Test_Case_ID}/attachments
The Auth type which I am using is Basic.
Here is a response which I am getting in postman
Can anyone let me know what I am doing wrong | what could be the cause behind this issue.
Or Else any alternate way or API resources to get Attachments for Jira-Zephyer Test cases?
You will need to use Zephyr scale API token as authorization to get a response for the APIs.
https://support.smartbear.com/zephyr-scale-cloud/api-docs/#section/Authentication

App Engine App failing with File(/base/data/home/.config/gcloud/application_default_credentials.json) is not within the allowed path(s)

My Google App Engine based website started failing suddenly with following error -
file_exists(): open_basedir restriction in effect. File(/base/data/home/.config/gcloud/application_default_credentials.json) is not within the allowed path(s):
Any help/pointers will be appreciated as my website is currently down because of it.
I post here another possible solution as I had exaclty the same error message, even the reason was different. This is why this question came up while I searched for it.
I am using the Google Translation API:
https://googleapis.github.io/google-cloud-php/#/docs/google-cloud/v0.153.0/translate/v2/translateclient
In my case I didn't provide in $translate = new TranslateClient(); the parameter key.
Providing the Google API key $translate = new TranslateClient([ "key" => "my-key" ]); fixed it.

Testing HelloSign API embedded signature

Hello I am using the HelloSign API, looking to test the embedded signing feature. How am I able to test the embedded document to sign on my test site? I am using the nodejs SDK along with AngularJS. Thank you in advance.
Here's the general walkthrough for embedded signing, which walks you through the server side and client side steps: https://app.hellosign.com/api/embeddedSigningWalkthrough
Here's an FAQ on testing locally: https://faq.hellosign.com/hc/en-us/articles/217048987-What-tools-can-I-use-to-test-the-API-and-callbacks-locally-
For greater detail, please write into apisupport#hellosign.com.
-First thing is create an account with Hellosign
Next thing is creating your API KEY from your registered account.
Create an API App with your registered hellosign account (This is important because during the setup it will ask for the URL where the Iframe will be created.)
Now to use it simply include this script (<script type="text/javascript" src="https://s3.amazonaws.com/cdn.hellosign.com/public/js/hellosign-embedded.LATEST.min.js"></script>).
And then finally do this in your client side component file
HelloSign.init("CLIENT_ID");
HelloSign.open({
url: "SIGN_URL",
allowCancel: true,
messageListener: function(eventData) {
// do something
}
});
And Voila..!! It will work.

WSO2 APIM 1.10 - config endpoint secure scheme while adding api via REST-API

I am using APIM 1.10 to add new APIs via the REST-API (see: https://docs.wso2.com/display/AM1100/apidocs/publisher/#!/operations#APIsApi#apisPost) and it works fine but:
I want to add the security-scheme: "Basic Auth" for the api endpoint.
But I have no idea how to do this, because the endpointConfig-config is not described.
I need something like this: endpointSecured:true, endpointAuthDigest:"Basic", endpointUTUsername:"usN", endpointUTPassword:"pass"
Any ideas?
C ya,
Marty
Following steps will help you to achieve the requirement.
Edit the API and go to the implementation tab.
Click on "Show More Options".
Select "Secured" for Endpoint Security Scheme.
Provide the credentials and save.
When you create API using rest API, you can add secure endpoint details by adding following part. &endpointType=secured&epUsername="admin"& epPassword="admin"
Here is a sample command
curl -X POST -b cookies http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d "action=addAPI&name=SampleAPI&context=/country&version=1.0.0&visibility=public&thumbUrl=&description=Check Country by Code&tags=country&endpointType=secured&epUsername="admin"& epPassword="admin"&tiersCollection=Gold,Bronze&http_checked=http&https_checked=https&resourceCount=0&resourceMethod-0=GET&resourceMethodAuthType-0=Application&resourceMethodThrottlingTier-0=Unlimited&uriTemplate-0=/*&default_version_checked=default_version&bizOwner=xx&bizOwnerMail=xx#ee.com&techOwner=xx&techOwnerMail=ggg#ww.com" -d'endpoint_config={"production_endpoints":{"url":"http://services.groupkt.com/country/get/iso2code/IN","config":null},"endpoint_type":"http"}';

How users could use registry Governance (GREG) to search for available services?

We needed to provide a tool where our customers (people) could search for published services. We're trying to use the Governance Registry but do not know the correct way to do so.
The easiest way to do this is by using the java API provided by WSO2. With this API you can browse and search through the registry.
Resource governanceFolder = registry.get("/_system/governance");
System.out.println("Folder description: " +
governanceFolder.getDescription());
// get the WSDL folder resource (use the url we browsed to)
String wsdlUrl = "/_system/governance/trunk/wsdls/_0/service_1" +
"/account/wsdl/trafficavoidance/accountService.wsdl";
Resource wsdlResource = registry.get(wsdlUrl);
// output the content of the wsdl
System.out.println(new String((byte[])wsdlResource
.getContent()));
List<Resource> paths = getServicePath(registry, "/_system/governance/trunk/services");
Configuring and setting up the client is a bit difficult. I've written a blog post on this a couple of weeks ago. So if you need more info you could look there: http://www.smartjava.org/content/access-wso2-registry-programatically
Following links might help you
-[1]https://docs.wso2.com/display/Governance460/CRUD+operation+support+for+Configurable+Governance+Artifacts
-[2]https://docs.wso2.com/display/Governance460/Configurable+Governance+Artifacts+with+API