Feature/screenshot fixes 2 (#50)
* Fixes #49 Fix the Deploy to Azure button * Update Lab 7 Security Screenshots * Update Lab 8 DevOps Screenshots * Update Lab 10 Additional Topics Screenshots * Clean up and remove obsolete screenshots * Fix wrong paths to images
Simon Kurtz
GitHub
|
|
@ -1,6 +1,6 @@
|
|||
|
||||
|
||||
<img style="float: left;" src="assets/images/APIM.png">
|
||||
<img style="float: left;" src="assets/images/apim.png">
|
||||
|
||||
# About this workshop
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ nav_order: 2
|
|||
|
||||
An instance can take some time to provision. Expect ~45-75 minutes. Therefore, please create an instance prior to any demo.
|
||||
|
||||
[](https://portal.azure.com/#create/Microsoft.ApiManagement)
|
||||
[](https://portal.azure.com/#create/Microsoft.ApiManagement)
|
||||
|
||||
Using either your own or [Azure's common naming convention](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming), fill in each required field and press *Review + Create*, followed by *Create* to provision the service. Once started, it is not necessary to remain on this page or in the Azure Portal. If you entered a valid email address, you will receive a provisioning completion email.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ In this section we provide you with a template architecture diagram for your api
|
|||
- What products are we going to define?
|
||||
- What teams and processess need to be in place to manage the Azure Apim?
|
||||
|
||||
|
||||
|
||||
| <a href="https://app.diagrams.net/#Uhttps%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fapim-lab%2Fmain%2Fassets%2Fdiagrams%2FapimADSv2.drawio" target="_blank">Edit As New</a>
|
||||
|
||||
Download Diagram:
|
||||
|
|
|
|||
|
|
@ -10,8 +10,6 @@ nav_order: 2
|
|||
|
||||
Some of the demos use the ColourWeb web application and the ColourAPI API application. In this lab we will show you how to deploy your own instances of the Colours Web and Colours API. Note - ColoursWeb / ColoursAPI is new version of ColorsWeb/ColorsAPI ... do not mix the web client and API versions.
|
||||
|
||||
|
||||
|
||||
The code for the ColourWeb / ColourAPI applications is available here:
|
||||
|
||||
- [ColourWeb](https://github.com/markharrison/ColoursWeb)
|
||||
|
|
@ -34,7 +32,7 @@ With the container we can deploy to multiple hosting options : VM's, App Service
|
|||
1. Login to Azure Portal at http://portal.azure.com.
|
||||
2. Open the Azure Cloud Shell and choose Bash Shell (do not choose Powershell)
|
||||
|
||||
|
||||
|
||||
|
||||
3. The first time Cloud Shell is started will require you to create a storage account.
|
||||
4. We proceed to create a unique identifier suffix for resources created in this Lab:
|
||||
|
|
@ -99,7 +97,7 @@ With the container we can deploy to multiple hosting options : VM's, App Service
|
|||
|
||||
Once we have a "Succeeded" message we proceed to navigate to the FQDN. And we should see our home page for our Colours Web:
|
||||
|
||||
|
||||
|
||||
|
||||
8. Now we proceed to create the ACI for the colors-api github container:
|
||||
|
||||
|
|
@ -135,4 +133,4 @@ With the container we can deploy to multiple hosting options : VM's, App Service
|
|||
|
||||
Once we have a "Succeeded" message we proceed to navigate to the FQDN. And we should see our home page (Swagger UI) for our Colours API:
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Azure Serverless (Functions and Logic Apps) can be configured to benefit from th
|
|||
|
||||
Example:
|
||||
|
||||
|
||||
|
||||
|
||||
```c#
|
||||
//string[] strColors = { "blue", "lightblue", "darkblue" };
|
||||
|
|
@ -29,29 +29,29 @@ Example:
|
|||
|
||||
Lets add the function to API Management. In the API blade select [+Add API] and the [Function App] tile
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the [Browse] button to get a list of Functions in the subscription
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the Function App and then the Function
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Amend the Names / Descriptions, URL suffix and select the Products
|
||||
|
||||
|
||||
|
||||
|
||||
- As previously add CORS policy
|
||||
|
||||
- Validate the function works - either from the Azure management portal or the developer portal
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Azure Logic Apps
|
||||
|
||||
|
|
@ -59,9 +59,9 @@ Lets add the function to API Management. In the API blade select [+Add API] an
|
|||
|
||||
Example:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Use the following sample message to generate the schema of the Request body payload. By specifying the schema, the individual fields (in this case `msg`) can be extracted and referred to in the subsequent logic
|
||||
|
||||
|
|
@ -73,34 +73,34 @@ Use the following sample message to generate the schema of the Request body payl
|
|||
|
||||
Lets add the function to API Managament. In the API blade select [+Add API] and the [Logic App] tile
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the [Browse] button to get a list of Logic Apps in the subscription
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the Logic App
|
||||
|
||||
|
||||
|
||||
|
||||
- Amend the Names / Descriptions, URL suffix and select the Products
|
||||
|
||||
|
||||
|
||||
|
||||
As previously add CORS policy
|
||||
|
||||
- Validate the Logic App works - either from the Azure management portal or the developer poral
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Check the Logic App audit
|
||||
|
||||
|
||||
|
||||
|
||||
- Check the email was sent
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -29,23 +29,23 @@ To deploy a self-hosted gateway:
|
|||
- Select `+ Add`
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Enter a Name and Location for the Gateway
|
||||
- Select the required APIs from those that are configured in the APIM instance
|
||||
- Our lab will use the Color API - this was configured in an earlier module
|
||||
- Select the `Add` button
|
||||
|
||||
|
||||
|
||||
|
||||
The added gateway will appear in the list ... this is the Gateway Deployment.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Click on the gateway in the list - a blade appears allowing further configuration
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the `Deployment` option from the menu
|
||||
- There are scripts for deploying on Docker and Kuberenetes ... for this lab, we will be using the Docker option
|
||||
|
|
@ -56,29 +56,29 @@ The added gateway will appear in the list ... this is the Gateway Deployment.
|
|||
docker run -p 80:8080 -p 443:8081 --name OnPremiseGateway --env-file env.conf mcr.microsoft.com/azure-api-management/gateway:latest
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
From a command line - elevated to Administrator (needed for Docker commands)
|
||||
|
||||
- Navigate to the location where the *env.conf* is located
|
||||
- Run the Docker run command
|
||||
|
||||
|
||||
|
||||
|
||||
The first time this is executed, it will need to pull down the Docker image - and so there will be a small delay. Subsequently - if restarted - it will just use the downloaded image.
|
||||
|
||||
|
||||
|
||||
|
||||
Once downloaded, the log output from the container will display a Sputnik logo (this was an internal code name) and some diagnostic logs.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Note that in the Gateway blade we can see the status - it will show there is one healthy Gateway Node connected to the Deployment. The Gateway Node will keep in sync, and be automatically updated should any of the Gateway Deployment config changes.
|
||||
|
||||
|
||||
|
||||
|
||||
## Testing the API
|
||||
|
||||
|
|
@ -88,15 +88,15 @@ Our Gateway Node is now deployed - and we can test that it works.
|
|||
- Open Notepad - make note of URLs including the key. For our lab test, the machine name is just *localhost*
|
||||
- https://localhost/color/api/RandomColor?key=Unlimited-Key
|
||||
|
||||
|
||||
|
||||
|
||||
- Use a tool like [Postman](https://www.postman.com/) to test the API ... should see the random color appear in the response and this confirms everything is working properly
|
||||
- If tested with a browser, then a warning needs to accepted to proceed - this is because trusted TLS certificates have not been set up
|
||||
|
||||
|
||||
|
||||
|
||||
Diagnostics for the API call will be logged by the container.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ A product contains one or more APIs as well as a usage quota and the terms of us
|
|||
|
||||
Press *Add group*, check *Developers* and *Guests*, then press *Select*. The two added roles are shown now.
|
||||
|
||||
|
||||
|
||||
|
||||
Back in the private browsing session, browse to *Products* and observe the new *Gold Tier*.
|
||||
|
||||
|
|
|
|||
|
|
@ -49,11 +49,11 @@ First, we need to enable CORS for the domain name of the frontend. To achieve th
|
|||
- Inside the `Inbound processing` area you will see the `cors` policy, which we added in part 2 by pressing the `Enable Cors` button.
|
||||
- Click on the pencil icon next to that policy to edit it.
|
||||
|
||||
|
||||
|
||||
|
||||
- Here we will see this form where we can add the domain name of our frontend `https://markcolorweb.azurewebsites.net` or the `*` for all domains. Press *Add allowed origin*, enter the URL, then press *Save*.
|
||||
|
||||
|
||||
|
||||
|
||||
- After enabling CORS in APIM lets go back to our frontend <https://markcolorweb.azurewebsites.net> and follow these steps:
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ The [cors policy](<https://docs.microsoft.com/en-us/azure/api-management/api-man
|
|||
|
||||
We have already configured the *cors* policy for our APIs in labs 2 & 3. Below is the resulting XML:
|
||||
|
||||
|
||||
|
||||
|
||||
```xml
|
||||
<policies>
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ To create an event hub within the namespace, follow these steps:
|
|||
|
||||
1. From the **Event Hubs** blade select **+ Event Hub**>
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type a name for your event hub, then select **Create**.
|
||||
|
||||
|
|
@ -137,7 +137,7 @@ Once your logger is configured in API Management, you can configure your log-to-
|
|||
1. Select **Show snippets**.
|
||||
1. In the window on the right, select **Advanced policies** > **Log to EventHub**. This inserts the `log-to-eventhub` policy statement template.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Replace the policy with this snippet:
|
||||
|
||||
|
|
|
|||
|
|
@ -7,15 +7,16 @@ nav_order: 1
|
|||
|
||||
## Security
|
||||
|
||||
In this lab, we are going to see how to use JSON Web Tokens with your APIs.
|
||||
|
||||
### JSON Web Tokens (JWT)
|
||||
|
||||
JSON Web Tokens are an open-industry standard method for representing claims securely between two parties. More info at <https://jwt.io/>
|
||||
JSON Web Tokens are an open-industry standard method for representing claims securely between two parties. More info at <https://jwt.io>.
|
||||
|
||||
- Use the following sites
|
||||
- <https://www.unixtimestamp.com/index.php>, in this website we need to get a date in the future using the epoch unix timestamp, be sure to get a timestamp at least 1 hour in the future, otherwise the JWT will not work.
|
||||
- i.e. 01/11/2029 = 1862842300
|
||||
- <https://jwt.io/> to create a JWT. Please add the following to your JWT
|
||||
- In the payload area use a similar payload to this one:
|
||||
Use the following sites:
|
||||
- <https://www.unixtimestamp.com> to get a future date using the Epoch Unix Timestamp _at least one hour from the current time_ as the JWT will not work otherwise (e.g. 01/11/2029 = `1862842300`)
|
||||
|
||||
- <https://jwt.io> to create a JWT with payload modeled after this one:
|
||||
```json
|
||||
{
|
||||
"sub": "1234567890",
|
||||
|
|
@ -24,31 +25,26 @@ JSON Web Tokens are an open-industry standard method for representing claims sec
|
|||
"exp": 1862842300
|
||||
}
|
||||
```
|
||||
- In the signature area use a key that matches the value in the policy expression e.g. `123412341234123412341234`, also be sure to check the option that says **secret base64 encoded**.
|
||||
- In the signature area use a key that matches the value in the policy expression (see below - e.g. `123412341234123412341234`). Also be sure to check the option that says **secret base64 encoded**.
|
||||
|
||||
- Your configuration should be similar as in this image:
|
||||
- Your configuration should be similar to this:
|
||||
|
||||
|
||||
|
||||
|
||||
### JSON Web Tokens (JWT) - validate
|
||||
|
||||
In this lab, we are going to see how to use the token with your APIs
|
||||
- Open the Calculator API 'Code View',
|
||||
- Add the inbound policy to validate the JWT. The example shows the use of variables in an expression - useful if a value is repeated.
|
||||
|
||||
#### JSON Web Tokens (JWT) - validate
|
||||
|
||||
Open the Calculator API 'Code View'
|
||||
- Add the inbound policy to validate that JWT is valid
|
||||
- The example shows the use of variables in an expression - useful if a value is repeated
|
||||
|
||||
```xml
|
||||
<!-- Inbound -->
|
||||
<set-variable name="signingKey" value="123412341234123412341234" />
|
||||
<validate-jwt header-name="Authorization" failed-validation-httpcode="401" failed-validation-error-message="Unauthorized">
|
||||
<issuer-signing-keys>
|
||||
<key>@((string)context.Variables["signingKey"])</key>
|
||||
</issuer-signing-keys>
|
||||
</validate-jwt>
|
||||
|
||||
```
|
||||
```xml
|
||||
<!-- Inbound -->
|
||||
<set-variable name="signingKey" value="123412341234123412341234" />
|
||||
<validate-jwt header-name="Authorization" failed-validation-httpcode="401" failed-validation-error-message="Unauthorized">
|
||||
<issuer-signing-keys>
|
||||
<key>@((string)context.Variables["signingKey"])</key>
|
||||
</issuer-signing-keys>
|
||||
</validate-jwt>
|
||||
```
|
||||
|
||||
- Invoke the API ... should get a [401 Unauthorized error]
|
||||
- Invoke the API with a request header containing the security token (got above from <https://jwt.io/>) ... should get a 200 success
|
||||
|
|
@ -57,14 +53,14 @@ Open the Calculator API 'Code View'
|
|||
|
||||
No JWT:
|
||||
|
||||
|
||||
|
||||
|
||||
Valid JWT in the header:
|
||||
|
||||
Note the bearer token in the Request payload.
|
||||
Make sure your JWT token has an expiry date in the future.
|
||||
|
||||
|
||||
|
||||
|
||||
#### JSON Web Tokens (JWT) - check a claim exists
|
||||
|
||||
|
|
@ -91,7 +87,7 @@ Make sure your JWT token has an expiry date in the future.
|
|||
|
||||
Checking for admin claim:
|
||||
|
||||
|
||||
|
||||
|
||||
Checking for adminx claim:
|
||||
|
||||
|
|
@ -99,7 +95,7 @@ Checking for adminx claim:
|
|||
<claim name="adminx" match="any">
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
#### JSON Web Tokens (JWT) - extract claim and pass to backend
|
||||
|
||||
|
|
@ -123,5 +119,5 @@ Checking for adminx claim:
|
|||
</set-header>
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ In Azure, an Active Directory identity can be assigned to a managed resource suc
|
|||
|
||||
#### Register API Management with Active Directory
|
||||
|
||||
|
||||
|
||||
|
||||
#### Key Vault - Create Key Vault and add a secret
|
||||
|
||||
|
|
@ -23,34 +23,34 @@ In Azure, an Active Directory identity can be assigned to a managed resource suc
|
|||
- Name:`favoritePerson`
|
||||
- Value: `3`
|
||||
|
||||
|
||||
|
||||
|
||||
#### Key Vault - Access policy and principal assignment
|
||||
|
||||
Create an access policy
|
||||
|
||||
|
||||
|
||||
|
||||
Select the `Get` operation from the list of Secret permissions
|
||||
|
||||
|
||||
|
||||
|
||||
Select the principal and search for the name of your API Management instance
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Remember to click **Save**
|
||||
|
||||
|
||||
|
||||
|
||||
#### API Management, Key Vault and Managed Service Identity
|
||||
|
||||
- Add a new operation to the Star Wars API
|
||||
- Update the policies for the new operation
|
||||
|
||||
|
||||
|
||||
|
||||
```xml
|
||||
<!-- Inbound -->
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Based on the Microsoft Tech Community [blog post](https://techcommunity.microsof
|
|||
|
||||
The API Management is a proxy to the backend APIs, it’s a good practice to implement security mechanism to provide an extra layer of security to avoid unauthorized access to APIs.
|
||||
|
||||
|
||||
|
||||
|
||||
In this Diagram we can see the OAUTH flow with API Management in which:
|
||||
|
||||
|
|
|
|||
|
|
@ -71,17 +71,17 @@ Every client application that calls the API needs to be registered as an applica
|
|||
- Then choose `My APIs`
|
||||
- Select the record for `backend-app-oauth`
|
||||
|
||||
|
||||
|
||||
|
||||
- Then select the `Delegated Permissions` option
|
||||
- Then mark the `Calculator.Read` checkbox
|
||||
- Then click the `Add Permissions` button
|
||||
|
||||
|
||||
|
||||
|
||||
- Finally click the `Grant admin consent for ...`
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Enable OAuth 2.0 in the Developer Console for Authorization Code Grant type
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Optional(if you want to deploy with a build pipeline):
|
|||
|
||||
## Architecture
|
||||
|
||||
|
||||
|
||||
|
||||
This is one example of how to use Azure DevOps Repo and Azure DevOps Pipelines to enable a Continuous Integration and Continuous Deployment (CI/CD) for API\'s on an Azure API Management Service. There're other ways to do this, but this is a \"Keep it Simple\" to help you start. (Planning to have another version using Github and Github Actions soon).
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ You have two choices when specifying your settings:
|
|||
|
||||
After executing the command above, you will see something similar to this:
|
||||
|
||||
|
||||
|
||||
|
||||
Then you see the JSON files extracted:
|
||||
|
||||
|
|
@ -146,10 +146,10 @@ We will use a **Build Pipeline** to pull the extracted files from a repo and put
|
|||
2 - Configure the fields as show bellow:
|
||||
|
||||
|
||||
generated](../../assets/images/ado-build-pipeline1.png)
|
||||
|
||||
|
||||
generated](../../assets/images/ado-build-pipeline2.png)
|
||||
|
||||
# Release Pipeline
|
||||
|
||||
|
|
@ -169,19 +169,19 @@ You can use [this](https://docs.microsoft.com/en-us/azure/devops/pipelines/relea
|
|||
|
||||
3 - Set set [Deployment mode to Incremental](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-tutorial-pipeline#create-a-devops-project)
|
||||
|
||||
|
||||
|
||||
|
||||
When you finish the steps above, you will see something like this:
|
||||
|
||||
|
||||
|
||||
|
||||
Clone your QA environment and update the **Resource Group** and **ApimServiceName** value on "Override template parameters" field to reflect your "production" APIM.
|
||||
|
||||
|
||||
|
||||
|
||||
Now you will see your Release Pipeline like this:
|
||||
|
||||
|
||||
|
||||
|
||||
By using a combination of manual deployment approvals, gates, and manual intervention within a release pipeline in Azure Pipelines, you can quickly and easily configure a release pipeline with all the control and auditing capabilities you require for your DevOps CI/CD processes. You will find more information on this [link](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-devops).
|
||||
|
||||
|
|
|
|||
Двоичные данные
assets/images/APIMAddAPIs.png
|
До Ширина: | Высота: | Размер: 77 KiB |
Двоичные данные
assets/images/APIMAddColorAPI3.png
|
До Ширина: | Высота: | Размер: 80 KiB |
Двоичные данные
assets/images/APIMAddColorAPI4.png
|
До Ширина: | Высота: | Размер: 126 KiB |
Двоичные данные
assets/images/APIMAddSWGetPeople.png
|
До Ширина: | Высота: | Размер: 85 KiB |
Двоичные данные
assets/images/APIMAddSWGetPeopleById.png
|
До Ширина: | Высота: | Размер: 84 KiB |
Двоичные данные
assets/images/APIMAddStarWars.png
|
До Ширина: | Высота: | Размер: 84 KiB |
Двоичные данные
assets/images/APIMCORS2.png
|
До Ширина: | Высота: | Размер: 111 KiB |
Двоичные данные
assets/images/APIMCORS3.png
|
До Ширина: | Высота: | Размер: 92 KiB |
Двоичные данные
assets/images/APIMCORS4.png
|
До Ширина: | Высота: | Размер: 115 KiB |
Двоичные данные
assets/images/APIMCalcTryIt2.png
|
До Ширина: | Высота: | Размер: 87 KiB |
Двоичные данные
assets/images/APIMCertBlade.png
|
До Ширина: | Высота: | Размер: 55 KiB |
Двоичные данные
assets/images/APIMColorWebConfig.png
|
До Ширина: | Высота: | Размер: 12 KiB |
Двоичные данные
assets/images/APIMDevKeys2.png
|
До Ширина: | Высота: | Размер: 64 KiB |
Двоичные данные
assets/images/APIMDevSubscribe2.png
|
До Ширина: | Высота: | Размер: 48 KiB |
Двоичные данные
assets/images/APIMDevTryAPI3.png
|
До Ширина: | Высота: | Размер: 84 KiB |
Двоичные данные
assets/images/APIMDeveloperPortal.png
|
До Ширина: | Высота: | Размер: 228 KiB |
Двоичные данные
assets/images/APIMFederatationGetAppID.png
|
До Ширина: | Высота: | Размер: 131 KiB |
Двоичные данные
assets/images/APIMFederationAuthentication.png
|
До Ширина: | Высота: | Размер: 117 KiB |
Двоичные данные
assets/images/APIMFederationAzureAD.png
|
До Ширина: | Высота: | Размер: 95 KiB |
Двоичные данные
assets/images/APIMFederationAzureAD2.png
|
До Ширина: | Высота: | Размер: 96 KiB |
Двоичные данные
assets/images/APIMFederationAzureAD3.png
|
До Ширина: | Высота: | Размер: 79 KiB |
Двоичные данные
assets/images/APIMFederationCreateApp.png
|
До Ширина: | Высота: | Размер: 80 KiB |
Двоичные данные
assets/images/APIMFederationCreateApp2.png
|
До Ширина: | Высота: | Размер: 74 KiB |
Двоичные данные
assets/images/APIMFederationCreateKey.png
|
До Ширина: | Высота: | Размер: 91 KiB |
Двоичные данные
assets/images/APIMFederationCreateKey2.png
|
До Ширина: | Высота: | Размер: 97 KiB |
Двоичные данные
assets/images/APIMFederationSignup.png
|
До Ширина: | Высота: | Размер: 31 KiB |
Двоичные данные
assets/images/APIMFederationSignup2.png
|
До Ширина: | Высота: | Размер: 59 KiB |
Двоичные данные
assets/images/APIMFederationSignup3.png
|
До Ширина: | Высота: | Размер: 28 KiB |
Двоичные данные
assets/images/APIMFederationSignup4.png
|
До Ширина: | Высота: | Размер: 38 KiB |
Двоичные данные
assets/images/APIMGitClone.png
|
До Ширина: | Высота: | Размер: 20 KiB |
Двоичные данные
assets/images/APIMGitClone2.png
|
До Ширина: | Высота: | Размер: 20 KiB |
Двоичные данные
assets/images/APIMGitClone3.png
|
До Ширина: | Высота: | Размер: 27 KiB |
Двоичные данные
assets/images/APIMGitDeploy.png
|
До Ширина: | Высота: | Размер: 86 KiB |
Двоичные данные
assets/images/APIMGitEditContent.png
|
До Ширина: | Высота: | Размер: 6.8 KiB |
Двоичные данные
assets/images/APIMGitProductUpdates.png
|
До Ширина: | Высота: | Размер: 39 KiB |
Двоичные данные
assets/images/APIMGitPush.png
|
До Ширина: | Высота: | Размер: 22 KiB |
Двоичные данные
assets/images/APIMGroupsBlade.png
|
До Ширина: | Высота: | Размер: 72 KiB |
Двоичные данные
assets/images/APIMIdentitiesBlade.png
|
До Ширина: | Высота: | Размер: 86 KiB |
Двоичные данные
assets/images/APIMListAPIs.png
|
До Ширина: | Высота: | Размер: 93 KiB |
Двоичные данные
assets/images/APIMManagementAPIBlade.png
|
До Ширина: | Высота: | Размер: 128 KiB |
Двоичные данные
assets/images/APIMMockingFrontend2.png
|
До Ширина: | Высота: | Размер: 120 KiB |
Двоичные данные
assets/images/APIMMockingFrontend3.png
|
До Ширина: | Высота: | Размер: 123 KiB |
Двоичные данные
assets/images/APIMMockingInbound2.png
|
До Ширина: | Высота: | Размер: 128 KiB |
Двоичные данные
assets/images/APIMMockingInbound3.png
|
До Ширина: | Высота: | Размер: 110 KiB |
Двоичные данные
assets/images/APIMOAuthBlade.png
|
До Ширина: | Высота: | Размер: 55 KiB |
Двоичные данные
assets/images/APIMOverviewBlade.png
|
До Ширина: | Высота: | Размер: 102 KiB |
Двоичные данные
assets/images/APIMProductStarter.png
|
До Ширина: | Высота: | Размер: 53 KiB |
Двоичные данные
assets/images/APIMProductStarterPolicy.png
|
До Ширина: | Высота: | Размер: 101 KiB |
Двоичные данные
assets/images/APIMRepositoryBlade.png
|
До Ширина: | Высота: | Размер: 85 KiB |
Двоичные данные
assets/images/APIMRepositoryPWBlade.png
|
До Ширина: | Высота: | Размер: 85 KiB |
Двоичные данные
assets/images/APIMResponseDeleteHeaders2.png
|
До Ширина: | Высота: | Размер: 118 KiB |
Двоичные данные
assets/images/APIMRevisionsAdd.png
|
До Ширина: | Высота: | Размер: 29 KiB |
Двоичные данные
assets/images/APIMSWCORS1.png
|
До Ширина: | Высота: | Размер: 90 KiB |
Двоичные данные
assets/images/APIMScale.png
|
До Ширина: | Высота: | Размер: 64 KiB |
Двоичные данные
assets/images/APIMSecurityRegisterPrincipal.jpg
|
До Ширина: | Высота: | Размер: 49 KiB |
Двоичные данные
assets/images/APIMTraceJWTClaimBackend.png
|
До Ширина: | Высота: | Размер: 31 KiB |
Двоичные данные
assets/images/APIMTraceNV.png
|
До Ширина: | Высота: | Размер: 171 KiB |
Двоичные данные
assets/images/APIMTraceNV2.png
|
До Ширина: | Высота: | Размер: 115 KiB |
Двоичные данные
assets/images/APIMTraceNV3.png
|
До Ширина: | Высота: | Размер: 29 KiB |
Двоичные данные
assets/images/APIMUserActivateSub.png
|
До Ширина: | Высота: | Размер: 102 KiB |
Двоичные данные
assets/images/APIMUserActivateSub2.png
|
До Ширина: | Высота: | Размер: 95 KiB |
Двоичные данные
assets/images/APIMUsersBlade.png
|
До Ширина: | Высота: | Размер: 72 KiB |
Двоичные данные
assets/images/APIMVNet.png
|
До Ширина: | Высота: | Размер: 69 KiB |
Двоичные данные
assets/images/APIManagement.png
|
До Ширина: | Высота: | Размер: 188 KiB |
Двоичные данные
assets/images/Architecture.png
|
До Ширина: | Высота: | Размер: 136 KiB |
Двоичные данные
assets/images/add-user-in-users-all-users.png
|
До Ширина: | Высота: | Размер: 99 KiB |
|
До Ширина: | Высота: | Размер: 30 KiB После Ширина: | Высота: | Размер: 30 KiB |
|
До Ширина: | Высота: | Размер: 40 KiB После Ширина: | Высота: | Размер: 40 KiB |
|
До Ширина: | Высота: | Размер: 62 KiB После Ширина: | Высота: | Размер: 62 KiB |
|
До Ширина: | Высота: | Размер: 30 KiB После Ширина: | Высота: | Размер: 30 KiB |
|
До Ширина: | Высота: | Размер: 71 KiB После Ширина: | Высота: | Размер: 71 KiB |
|
До Ширина: | Высота: | Размер: 28 KiB После Ширина: | Высота: | Размер: 28 KiB |
|
До Ширина: | Высота: | Размер: 136 KiB После Ширина: | Высота: | Размер: 136 KiB |
|
До Ширина: | Высота: | Размер: 73 KiB После Ширина: | Высота: | Размер: 73 KiB |
|
До Ширина: | Высота: | Размер: 242 KiB После Ширина: | Высота: | Размер: 242 KiB |
|
До Ширина: | Высота: | Размер: 177 KiB После Ширина: | Высота: | Размер: 177 KiB |
|
До Ширина: | Высота: | Размер: 204 KiB После Ширина: | Высота: | Размер: 204 KiB |
|
До Ширина: | Высота: | Размер: 207 KiB После Ширина: | Высота: | Размер: 207 KiB |
|
До Ширина: | Высота: | Размер: 190 KiB После Ширина: | Высота: | Размер: 190 KiB |
|
До Ширина: | Высота: | Размер: 267 KiB После Ширина: | Высота: | Размер: 267 KiB |
|
До Ширина: | Высота: | Размер: 236 KiB После Ширина: | Высота: | Размер: 236 KiB |
|
До Ширина: | Высота: | Размер: 66 KiB После Ширина: | Высота: | Размер: 66 KiB |
|
До Ширина: | Высота: | Размер: 130 KiB После Ширина: | Высота: | Размер: 130 KiB |
|
До Ширина: | Высота: | Размер: 99 KiB После Ширина: | Высота: | Размер: 99 KiB |
|
До Ширина: | Высота: | Размер: 246 KiB После Ширина: | Высота: | Размер: 246 KiB |