I created projects in Design Center and then publish to exchange. I tried to edit portal of my asset created in Exchange through REST method - PATCH https://anypoint.mulesoft.com/exchange/api/v1/organizations/{organizationId}/assets/{groupId}/{assetId}/v1/portal. But I got 404 error asset portal not found. But my asset is definitely in Exchange
The endpoint you mentioned is to publish the content of the public portal that is in the draft mode.
Please review that all the following items are correct:
Did you create a draft first before trying to publish it?
Are all the query parameters ({organizationId}, {groupId}, {assetId}) replaced with the correct values?
Is the version correct? It seems that the REST documentation of the API doesn't mention that the last v1 is the version to be replaced by the asset version.
See https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/exchange-experience-api/minor/1.0/pages/Public%20Portal/ for more information.
Related
Authorize.Net will be changing from Akamai SureRoute as the CDN to CloudFlare. Here is the announcement.
The article mentions:
Phase 2 (October 15, 2019 ~10:00am PT) – We will automatically be directing all Sandbox api sites/traffic directly to our network.
Needed Action: Ensure certificate is installed/trusted by
host/solution, Entrust L1 K certificate. Please consult with your
developer/solution provider. If certificate is needed please see
support article: How do I obtain Authorize.Net Certificate for my
host/solution provider?
The above link to obtain the Authorize.Net certificate points to Entrust.Net, which lists various options to purchase the certificates.
We provide Authorize.Net integration using the dotnet sdk. Which I installed as a Nuget package.
How do I find out if we do need a certificate? If we do, do I have to purchase it from Entrust?
I have gone through the link provided by authorize.net(https://support.authorize.net/s/article/Authorize-Net-Network-Change-FAQ) and i checked my code for the API endpoints specified in the link content.
We are using the Akamai end point for the transaction in production(PHP SDK for Authorize.net).
I have used the Akamai endpoint https://api2.authorize.net/xml/v1/request.api in my code for production.
As of my understanding If you are using Non Akamai API endpoint you don't have to change anything in the code or in server.
Please check your code and find the Endpoints used for transaction.It will help you to identify the actions you have to do before the network change.
Reference :- https://support.authorize.net/s/article/Authorize-Net-Network-Change-FAQ
What about URLs not on Akamai? The API endpoints not on Akamai will
not be changing or impact and will continue to function as they do
today. Needed Action: No actions or changes. Production API Urls:
https://api.authorize.net/xml/v1/request.api
https://api.authorize.net/soap/v1/Service.asmx
https://secure.authorize.net/gateway/transact.dll
Latest Discussion in authorize.net community forum :-
https://community.developer.authorize.net/t5/Integration-and-Testing/Confused-About-Certificate-Requirements-On-Network-Change/m-p/69610
We are currently having all our APIs in Azure API Management Portal. The versioning in the API code is handled using the version header. These APIs were deployed into our Production environment mid of Last year. I guess we did not have the versioning concept in the Old API Management Portal and the vendors who are using the APIs which are in Production works without passing the version header (if the version header is not passed, it will fallback to the initial version).
We could see that, currently API Management does have ability to create versions. But, if I create a new version for the existing API – I could see that the existing version (which currently works with or without version header) stops working. It is giving resource not found error. If we go into the API settings page for the Existing version, we could see that the Version Header field is mandatory and not filled.
Is there any way we can default the version header to the initial version through API Management?
This is old but probably worth answering for someone asking in the future.
You can set a header on all API operations in the Azure portal.
Select the API version and then ensure All operations is selected in the list of operations.
Then in the Inbound Processing section click + Add policy.
Set headers is one of the options.
Select that and add the details for the header.
Save and repeat for the other versions you have defined, obviously setting the correct version each time.
Hope this helps.
You may also define passing the version as a header parameter when initially adding the API to API Management as Open API Specification Full definition and then set the Header definition in Versioning scheme.
I've got a program which creates JIRA issues using the jira-rest-api supported by Atlassian.
What I'd like to do is to create a link within the issue to an external URL (actually a presigned Amazon S3 link).
At the REST level this should be doable with a POST request to the Jira api to create a remoteLink. However I cannot find methods in the client APIs or a RemoteLink dto in the Java library.
Nor does the Java library appear to give any access to lower level REST handlers.
Now, I could set up my own REST handling code, going right back to the endpoint URL and authentication, but that's messy, when most of the code the code should already be there. Also I can't clearly see which json fields are required, and which not can be left to the API.
Am I overlooking something obvious in the documentation? I can't even seem to locate source for the client implementation, only the interface layer.
My current code is using version 3.0.6 of the api, but I've just checked v4 (which seems to be the latest on offer) and there's still no RemoteLink support.
Have you tried with these?
Server: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.26380925.1321063199.1523351418-1788196903.1491202928#api/2/issue-deleteRemoteIssueLinkById
Cloud: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-issueIdOrKey-remotelink-linkId-delete
https://new-console.ng.bluemix.net/docs/services/apiconnect/apic_tutorial.html#apic_tutorial_01
Follow previous link to do create loopback project named ibmsvt and do test locally, we can post and get.
then publish this api as running api app on bluemix and we will get api target url and tls file.
type url and tls in api designer invoke, and publish api product again.
check api connect service and we can find that published api product has been published, configure developer portal, and invite developers
login developer portal and register one app
subscribe app to api product and run post command.
We will see that we only get can't post error information...
Please see attachment info for error info and api file.
From the screen capture provided, it looks like you're displaying the logs for the loopback application deployed on bluemix. It also looks like the POST request from APIConnect hit the Bluemix application as well. However, I'm unable to see the exact message of the error. What error did you get when you execute the POST from APIConnect? I suspect the POST did not include the $(request.path), what did you change the invoke url to be ? Can provide the x-ibm-configuration section in your yaml file? It will be located in your /definitions.
Thanks and best regards,
I am just have the exact problem, and struggled for days on redoing the tutorial several times, but still met with the same problem until found the upper reply, and gave me a hint.
In the tutorial, it says like the following:
Update the following fields with the values you copied previously:
Invoke URL: Insert the API target URL. You must specify the secure protocol HTTPS. For example:
apiconnect-ca3283b0-525c-488d-993b-3ab72fca78d0.youremail-dev.apic.mybluemix.net
TLS Profile: Insert the API invoke tls-profile.
For example:
client:Loopback-client
The origininal URL is $(runtime-url)$(request.path)$(request.search).
And the correct URL after updating is like following:
https://apiconnect-ca3283b0-525c-488d-993b-3ab72fca78d0.youremail-dev.apic.mybluemix.net$(request.path)
no slash before $(request.path), and $(request.search) should be deleted.
I also checked a tutorial video, it also do like this, but the screen for this step is passed away very quickly, you will not pay attention to this detail normally.
https://www.youtube.com/watch?v=Qku71JLv8vA&list=PLFa8jnU0KqE2eW5E449ziaurv8obSbcou&index=3&cm_mc_uid=24774488665514672571374&cm_mc_sid_50200000=1468400063
How to retrieve and call a Service's URL stored in WSO2 Governance Registry "GREG" by providing the service name; is there any simple Java method provided by the GREG API to get exactly and only the url of a service and not the whole Metadata ?
Thanks.
Ouufff finally, spent the entire night to solve this problem:
Registry governanceRegistry = GovernanceUtils
.getGovernanceUserRegistry(registry, username);
**// All governance artifacts should be loaded.
GovernanceUtils.loadGovernanceArtifacts((UserRegistry) governanceRegistry);**
ServiceManager manager = new ServiceManager(governanceRegistry);
But i stil don't know why all governance artifacts should be loaded before using it.
Please refer Governance Artifact Search Sample documentation,it's demonstrating how to search governance artifacts using attributes and get the paginated results. You can refer this blog as well.