Google APIs Console: Error Creating OAuth 2.0 Client ID - google-analytics-api

I am trying to use the Google APIs Console to create an OAuth 2.0 Client ID as a Service Account. This ID will be used to query my Google Analytics data through the Analytics API. However, when I attempt to create the Client ID, the APIs Console displays the message, "An error has occurred. Please retry later." I have tried several times throughout the last two weeks, but I keep getting the same error message. Can anyone advise me on what I'm doing wrong? Or is there another way that I can access my Analytics data via the API without an OAuth Client ID?

I figured out the issue. Apparently, the Google APIs Console does not allow a collaborator account to create new OAuth Service Accounts, only the owner account can do so.

Related

Connecting to the Skubana API

Has anybody made a REST connection to Skubana before? I have the app Key and Secret, but there is no more documentation about the handshake. I'm using Postman. Any insights into connecting to their API would be greatly appreciated.
After creating an App with Skubana I got an email which told me to create a trial account and then how to install the app on the trial account. There is then a further process to get the token which is required to access that trial account via the API. I have not seen those instructions anywhere except in the email. The API documentation is a little terse.

Insert webproperties via api whitelisted for project but still not working

I have requested beta access to google analytics api (in order to create webproperties via api) for a project and I received the confirmation email that the project has been whitelisted to use those resources.
I have created a service account and added the email of that service account as a user of a google analytics account where I would like to create webproperties. Then I get the token with proper scopes for google analytics (I put them all for testing, just in case:
"https://www.googleapis.com/auth/analytics",
"https://www.googleapis.com/auth/analytics.edit",
"https://www.googleapis.com/auth/analytics.manage.users",
"https://www.googleapis.com/auth/analytics.provision",
"https://www.googleapis.com/auth/analytics.readonly",
"https://www.googleapis.com/auth/analytics.manage.users.readonly"
I am able to call the webproperties list method without any issue but when I try to insert a new webproperty I do always receive: Error 403: Your project does not have access to this feature., insufficientPermissions.
Now it is a few days that I should have got access, but I could not manage to use those beta resources.
thanks a lot for your help
kind regards,
R

Receiving ACCOUNT_LACKS_PERMISSION_TO_CORRECT_TABS from Rest API; where is this permission configured?

I have an application that's been running just fine for a couple of years. Recently I'm getting the error message ACCOUNT_LACKS_PERMISSION_TO_CORRECT_TABS when attempting to add tabs to a newly added signer using a POST .../recipients/[recip-id]/tabs request to the REST API. I'd guess this permission is configured in the DocuSign console, but I'm not finding it there. Anyone know what controls this?

Single Sign-On on Bluemix: how to retrive user profile after binding SSO service to Liberty

I create an app, and bind it to Liberty. It works fine. But how could I get the user profile after user login?
I saw there is a "Return-to url" in integration tab:
https://ssoConfigboard.mybluemix.net:443/oidcclient/redirect/rwuYaLiy78
But after I visit this url, I got 500 server error:
Error 500: SRVE0295E: Error reported: 500
Anybody can help?
I ran into this same issue using Liberty with the BlueMix SSO service and found this link to be extremely helpful: https://www-304.ibm.com/connections/blogs/sweeden/entry/getting_started_with_ibm_single_sign_on_for_bluemix?lang=en_us
The key point here is that the user info is embedded in the Hashtable of the private credentials. This is not obvious at all. If you download the source code included with this blog you'll find a Java class called: UserHelper.java. This class will extract things like the user name and e-mail address from the WSSubject.
I ended up providing a REST interface in my web app that will allow users that are authenticated using oAuth to access their own user information.
I think one of the reasons this is all so cryptic is that there is a hole in the Java oAuth API standards in this area so this WSSubject class was a workaround to provide a way to access this information.

OAuth 2.0 in background while creating events on GCAL from Salesforce using Google Calendar API v3 (REST API)

My Situation:
I'm trying to populate a shared Google Calendar when an event is created on the Salesforce interface. Im currently using the latest Google Calendar v3 (RESTful) API for the same https://developers.google.com/google-apps/calendar/ with APEX my development language.
I'm using a trigger that catches all the value from the fields (trigger.new) and passing those values to a class that does the JSON serialization, authentication and API call.
Till now, I was able to get all the data from the object and pass is to the class and get it serialized. But I need to do the OAuth 2.0 call before I can make a Google Calendar API call. https://developers.google.com/google-apps/calendar/
I have setup my application on the Google API Console and obtained the Client ID, Client Secret etc.
The usual way OAuth 2.0 works is that an authentication page pops-up waiting for the user to grant access to the API so that it can access the calendars linked to the users account.
My question:
Is there any way I can get the OAuth done in the background using a static/private key which is either obtained by granting access just once but not every time or just programmatically using the key value in the class to authenticate the user.
Looking forward to getting useful suggestions/inputs/help from everyone.
If the user --once-- have made the authorization you got the access_code and the refresh_code.
I found it helpful to store both codes with the application (here Firefox and password manager). With the next start of the application (Firefox/extension) I use the refresh_code to request a new access_code. That is used during the session for any further calendar call.