developer-portal | Feedback House Developer Portal | Portal library

Azure APIM itself doesn't act as an identity provider like tyk but instead uses Azure AD (or rather any OAuth 2.0 provider).

The configuration in the docs is primarily to get the Developer Portal Console (the one used to test APIs) to work. For the actual API calls, there is no configuration required.

The validate-jwt policy is what takes care of preauthorization of requests.

Since you are looking for the client credentials flow alone, you could simply expose a portal that can create the required app registrations on your Azure AD using the Microsoft Graph API and expose the client id/secret to your users.

The current developer portal doesn't support this as of today but is something you could contribute to if you wish.

OK, solved (with the help of Microsoft support who sent a screenshot of the method being invoked on their side).

It seems that the method is not to be invoked from management.azure.com like all the other methods. Nope. It has to be invoked from the Management API URL that can be found in the Management API section of your APIM in Azure.

Curiously, the management API toggle does not even have to be on.

Your GET request should be like this:

https://my_apim_instance.management.azure-api.net/subscriptions/my_subscription_id/resourceGroups/my_resource_group/providers/Microsoft.ApiManagement/service/my_apim_instance/identity?api-version=2019-12-01

Now cue in the ever-helpful posters with ever-useful post-solution advice.

There is no built-in command in azure powershell to publish the dev portal, your option is to get the sas token with your service principal and invoke the api via powershell.

First, Make sure the setting Enable Management REST API is Yes in the azure portal.

Then use the commands below.

Follow these steps :

1. Right click on the JAR file.
2. Click Open with other Application.
3. Select the Archive manager according to your OS.
4. Open the component.xml file that is inside META-INF directory using a text editor.
5. Edit that text file and Save
6. Restart the server

If you running this without a container orchestration system, then you can mount these configurations to the docker container as volumes.

https://docs.docker.com/storage/volumes/

If you are using K8s or any container orchestration system, then in K8s you can use configmaps to add these files.

https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/

In both cases, you are not editing files in the container and simply replace these files.

This caching issue happens from time to time. Please clean the session in the browser and Ctrl +F5

A remote service is unreliable.

Program defensively by handling anticipated errors in your code. Consider implementing an exponential backoff with maximum retries. Also, add logging to track with requests were successful, retried or completely failed. If necessary you may want to implement application monitoring or paging system to alert you if a certain condition is met (100 errors in a row) if this is considered a process critical to your application.

Also, the service may have a bulk API that you can use, so instead of submitting n requests (where n is the number of player ids) you can submit n / bulk_limit (where bulk_limit is the max number of ids their bulk api accepts to process in a single request).

I have found a solution to what I'm trying to accomplish in this great detailed tutorial: https://serverless-stack.com/. Probably the most eloquent tutorial I've ever come across. I'm surprised that such information is so hard to find. AWS docs and tutorials are very poorly maintained and other than general concepts are not very helpful.