I have an up and running wso2 apim 4.0.0. I have created some subscription policies in admin portal, then applied them on certain apis on publisher portal. Now if I remove them on admin portal after unchecking on publisher, I am not able to change the api.
The UI of the publisher keeps popping up the message - "Something went wrong when updating the api". Wso2carbon.log prints
TID: [-1234] [api/am/publisher] [2022-05-18 14:31:38,333] ERROR
{org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl} - Error while updating
the API : 008d1f21-56b9-4356-a335-3c190ae9e86c - Specified tier(s) [Minimum] are invalid
org.wso2.carbon.apimgt.api.APIManagementException: Specified tier(s) [Minimum] are invalid
******************************************************************************************
TID: [-1234] [api/am/publisher] [2022-05-18 14:31:38,499] WARN
{org.wso2.carbon.apimgt.impl.utils.APIUtil} - Unknown tier: Minimum found on API:
MyApi
The question is why it keeps looking for the deleted tier if it is not used (unchecked) in subscriptions on publisher portal?
How to safely delete the custom subscription policy so that I can avoid aforementioned error?
I can also experience the same behavior with the product.
As a workaround, I was successfully able to get the API back as below:
reload the API if it's not loaded after the deletion
go to the subscriptions tab of that API
if there are no subscription policies available as selected select any of them and click save (if there are any selected ones available, just click save)
Go to the Business Info or Basic Info tab and click Save to see if it still comes
Further preventing deleting subscription policies assigned to APIs I have opened a git issue [1]. You can track the issue there.
[1] https://github.com/wso2/api-manager/issues/135
Related
I'm using the VSC Teams Toolkit. But when I sign in to my Azure account to provision my files, it says "No subscriptions discovered" as shown below:
Which subscription should I get to proceed with provisioning the files?
As the information explained, your logged-in Azure account doesn't seem to have associated Azure subscription.
You can login to your Azure portal, and under subscriptions, please check whether you have accessible subscription.
I had the same issue. You really need to go to portal.azure.com -> Subscriptions and have at least 1 subscription listed in the table below.
If no subscription is available, create new one - Pay as you go.
Then, in VS Code - sign out, sign in and subscription will be available
If vscode is complaining about not have an active subscription in the Teams Toolkit extension, for one make sure the tenant id is added to vsocde. See here enter link description here and here enter link description here
New Matillion user, and my first project is to read in Google Analytics data by using a google account authorized to access GA data from several clients.
I follow the steps from this Matillion documentation: Google Query Authentication Guide
I have setup the needed client ID and client secret, and I've pasted the redirect URL into the credentials page in the Google console.
From Matillion, I enter the client ID and secret in the OAuth Configuration dialog, and I configure the proxyserver and proxyport under "advanced connection options" as specified in the Matillion documentation.
When I click the Authorization link in the OAuth it opens a new tab to the Google page where I login and allow the access. Once I do this, the redirect seems(?) to kick in and I presented with a browser page with the message "Authorisation complete Please close this tab". I am not taken back to the tab where Matillion OAuth configuration is still waiting for a response of some type.
Any ideas with this? Additional information: I setup Matillion via the Snowflake Partner Connect console and am still in the free 14-day trial for Matillion.
I was able to get the OAuth workflow to finish. Any issues from this point forward will be a battle for another day. Here are my findings:
First note that I initiated my Matillion install from the Snowflake Partner Connect, which was very straight forward. I was up and running with Matillion in less than a minute.
The Matillion version that launched was 1.50.6, which is behind the most current version 1.58.4. I had no idea this would not be the most current version, as I assume the cloud platform might provide new installs with the latest version. I can see reasons why this might not be the case.
After several hours ensuring my GCP project, client id, client key, and other settings were correct everywhere, the workflow still would not complete. I opened a support case with Matillion and it was responded to within 2 hours. That is excellent. The first recommendation was to update Matillion to the latest version as it will address an OAuth issue resembling the one I reported. I saw the new version was very recent, and didn't realize I was nowhere near having the latest version.
After the update completed, I tried repeating all of the same steps. The only difference now was that the "Authorisation complete" tab closed on its own returning me to the Matillion tab which still sat "Waiting for response from service...". The version update seemed to show promise but not a solution.
A comment Schepo above cleared the final hurdle: I removed the proxyserver and proxyport "Advanced Connection options" from the OAuth configuration, and then tried getting a new authorization link. Matillion froze up and the session was dead. I had to close the browser, open a new incognito window and repeat the steps - without the proxyserver/proxyport connection settings. This time the workflow completed!
The Matillion documentation for Google Query: https://documentation.matillion.com/docs/2339840 should be updated if the Proxy Settings are not required for all OAuth configurations. The OAuth issue I reported should also be documented somewhere as a known issue addressable by the latest version (if not already).
OAuth being one of the many ways you can set up connectivity with Snowflake; it appears you're attempting to set up External OAuth, that is Google is the authorizing server. My understanding is that there are two paths to setting up OAuth,
This link has the Azure AD setup with the two options, https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself
Googling to setup Google AD returns https://support.google.com/cloud/answer/6158849?hl=en
You may have to follow a similar process, follow this content here: https://docs.snowflake.com/en/user-guide/oauth-ext-custom.html
After numerous exchanges with LinkedIn "Experts" none of them was able to help and do anything but copy paste the FAQ.
I'm preparing a client's platform for the v2 migration and encountered major problems for getting user data.
I currently have access to many fields including the r_basicprofile as can be seen in my app's auth tab:
However upon requesting the endpoint
/me I get the following error:
Not enough permissions to access: GET /me
I have also searched the new API documentation and there is no mention on how to request access to the r_basicprofile same on the FAQ the only link I could find was this one:
https://developer.linkedin.com/partner-programs
However it doesn't specify which one gives access to r_basicprofile
Our app is aimed at professionals and we require access to more info than just first, last name and email. Currently we work with positions, headlines and more.
How can I get access to the r_basicprofile and specifically the following fields:
'headline','summary','positions','specialties','location','industry','current-share','num-connections','num-connections-capped',
I'm having intermittent issues with signing in to LinkedIn with the LinkedIn Sign In API.
By intermittent I mean, I have two LinkedIn accounts, and as of this week one of them is unable to use the API to sign in to external services, such as the LinkedIn application I develop.
I'm authenticating via Auth0, whose engineers have confirmed there is an issue:
Over the last few weeks, the current version of the LinkedIn API for
sign-in has been intermittently failing when fetching the user
profile, causing a small number of users to fail to log in. The cause
of this issue is currently unknown, and is coming from LinkedIn
directly.
https://community.auth0.com/t/linkedin-connection-deprecated/20484/18
The Auth0 response i'm getting is the following (I've replaced senstivie response values with 'XX'):
{"name":"a0.response.invalid","message":"unknown error","json":{"error":"invalid_request","error_description":"InternalOAuthError: failed to fetch user profile (status: 500 data: {\n \"errorCode\": 0,\n \"message\": \"Internal API server error\",\n \"requestId\": \"XX\",\n \"status\": 500,\n \"timestamp\": 1550474289966\n})","state":"XX"},"status":0}
I know this API is being depreciated in March, but it's imperative that this API continues to work until the decommission date. I'm wondering if anyone has found a work around or solution to this issue, as it's impacting my ability to run real-world trials of my application scheduled in this week.
I've contacted LinkedIn support who directed me here.
Auth0 recently released a change to LinkedIn social connection, allowing you to use the new LinkedIn API (Version 2). You can change this by going to Connections-->Social-->LinkedIn-->Strategy Version dropdown and select Version 2. This should fix most of the login issues with the old deprecated version of LinkedIn API. More information post.
Our Marketplace application ID is 691703567391.
https://www.google.com/enterprise/marketplace/viewListing?productListingId=3198+1842896415262219465
Since 4-5 days, the application cannot access any customer data from the marketplace by using provisionning API and group provisionning APIs.
(apps-apis.google.com/a/feeds/group/#readonly and apps-apis.google.com/a/feeds/user/#readonly)
Whatever request our application is making, the response is always :
Error
401(Client Error)!!1
401.
That's an error.
There was an error in your request.
That's all we know.
For instance we did the GET request on the following URL : https://www.google.com/m8/feeds/contacts/default/full?xoauth_requestor_id=stef#gappsexperts.com and reponse was error 401.
After checking in cloud.google.com console, it appears that the Oauth1 reigtsred app has completely disappeared from our Cloud console (see screenshot)
Now only the Oauth2 app is available. I AM SURE THIS IS THE CAUSE OF THE PROBLEM.
Now here are the abnormal behaviours :
1/ We are getting errors for any request we make on user or group provisionning
2/ Oauth 1 registered app is not in the cloud.google.com console anymorre for this listing.
3/ WE CANNOT UNPUBLISH the listing in Google Apps Marketplace.
help us !
Is it possible you tried to create an OAuth 2 client ID in the same Developer Console project as your original Apps Marketplace developer console project?
I believe that might be a cause of this issue.
Your screenshot didn't come through in the post.