I am new to alfresco. I have alfresco cloud account and I want to access content in cloud repository. But I unable to figure out repository url for same.I need repository url format to connet to alfresco cloud account.
Thanks in advance.
The URL for CMIS 1.0 and the AtomPub binding is:
https://api.alfresco.com/cmis/versions/1.0/atom
You may also be able to use CMIS 1.1, just change the version number. I believe the browser binding may now be supported on Alfresco in the cloud. To try it, just change /atom to /browser.
Alfresco in the cloud uses OAuth so you'll need to do the "OAuth dance" to exchange your API key and secret for a bearer token. There are multiple OAuth clients available that will work with Alfresco in the cloud. For an example of how to use the Google OAuth client you might want to look at this project on Google Code.
If you don't have an Alfresco in the cloud API key you can get one for free from https://www.alfresco.com/develop/cloud/signup.
Related
I'm looking for documentation detailing the API that allows clients to connect to Firebase Remote Config. I'm making a Unity project for a platform other than mobile, and I've built my own client code for other Firebase products since no client library is available to my knowledge; now, I'm looking to do the same for Remote Config but I can't seem to find any documentation for the actual REST API!
I'm aware of the Remote Config admin/configuration API, but this is NOT what I'm looking for, as it is built for developer/admin accounts to modify remote config data; instead, I'm asking for the API that the official Firebase client libraries use to fetch one single user's configuration.
A link to official or unofficial documentation or easy-to-read sample code would be greatly appreciated! Otherwise, I might end up reverse engineering the Google-provided client libraries and generate some myself.
firebaser here
There is currently no publicly documented REST API for accessing Remote Config data from a client. The only supported platforms are the ones for which an SDK is available.
Also see:
Firebase Rest api for remote config
Calling Firebase Remote Config REST API without auth
How to query firebase remote config rest API, where somebody tries to use the (afaik undocumented) REST API in a web app
I am using firebase to allow users to upload their files to the Storage buckets. I was using the getDownLoadURL() to fetch the publicly available URL...however, this comes with an embedded token to allow access to the file.
In my same app, I'm using the Google Document viewer which takes a URL to preview the doc. Unfortunately, the Google Doc Viewer does not work with the firebase URLs's with the embedded token.
In Google Console, on an individual file, I click to make it public. In that case, the URL is now reachable via the https://storage.googleapis.com// format...and I don't need to use the token which works great.
So, what I want to do is mark/make a file public when I'm uploading it to firebase. I have reviewed the firebase docs and there doesn't seem to be a makePublic() method like there is on the Google API's.
Is there a way I can mark a file as public during upload, so that it can be accessed without any token?
The other solution was that I could update the bucket to be accessible, but this makes it totally open to be browsed at https://storage.googleapis.com/, which I don't want to do.
The client-side Firebase APIs don't know anything about the underlying Google Cloud Platform configurations for public content in storage buckets. So that won't be an option.
You will have to involve some backend code to change the object's configuration after it's uploaded. You could set up your own API endpoint via Cloud Functions (or whatever backend you want) to run one of the Google Cloud Storage server SDKs to set the file as public. (You will probably also want some way to authorize that the user calling your API should be able to make this change.)
I am using WSO2 API Manager to expose few APIs. But I don't want that the consumer use the API store for the subscriptions. The creation of subscriptions/applications and Access tokens should be managed through by my custom web application.
I have checked the WSO2 API Manager docs https://docs.wso2.com/display/AM210/apidocs/store/ and imported the swagger in SoapUI. When I try to invoke the store api of my local API Manager I am getting the HTML content of API store page. see below screenshot.
Can anyone please help what I am doing wrong? Or is there any other way to the requirement.
You need to pass token which is generated by passing scope and client secret key and password as described in https://docs.wso2.com/display/AM210/apidocs/store/#guide
Is there support for Proof Key for Code Exchange by OAuth Public Clients on Apigee cloud? I couldn't find any reference to it on the online documentation. If not supported, is it on the roadmap?
this should be fairly simple to do, all you need is to create the proper policies in your oauth proxies... we have a solution for openid connect on top of apigee and just added this in a few hours.
PKCE just requires that you store the code_challenge in a cache you can retrieve when about to create the access token, and then it requires you be able to re create from code_verifier + method... this can be done with a node backend, or by importing the proper libraries in a JS callout ( or java callout if that is your thing.)
we used node for this
I would like to use the google cloud datastore from Android, so I would not have to set up cloud endpoints et al. Trying the snapshot 1.0.0 libs, the only way to add credentials seems to be via a file name to the private key file. That does not sound right for Android, is there some better way, ideally with an Android example?
You should be able to use the AccountManager for identity management and authentication storage, see https://code.google.com/p/google-api-java-client/wiki/Android.
You should be able to use the Oauth2 flow to get the appropriate credentials, and just pass that in to the DatastoreOptions.
Note that the Cloud Datastore API does not support fine grain ACLs, so the user will have to be an admin of your Project in order to access the API.