call-api | Call API is a front-end layer

Dumb question, but I cannot find it. Why does IIS express use 2 ports (Sample file below).

Secondly, in this exercise here, when I'm requested to setup an app, it references 3007, which I cannot access. https://docs.microsoft.com/en-us/learn/modules/identity-application-types/5-exercise-web-apps-call-apis

Thanks in advance for any help you can give me. As mentioned in the title, I'm attempting to fight my way through an intro course and I'm struggling pretty hard with this particular issue.

HERE IS WHAT I NEED TO DO:

"Now we can start using APIs to get information from others applications. Lets create a Weather app like this one.

this project consist on create an app that takes the name of any city via input and display the current weather and the weather for the next 7 days.

The main point of this project is learn how to get info from the API and handle multiple promises.

You will get the input value (city name) from the element with the 'id=city' in the index.html file.

Each time the user clicks the 'search' button the program has to get the city name from the input (validation is required) and make the API call. Write all the javascript code in 'weather.js' file.

You need to create an account in OpenWeather and then you will be able to get an API KEY how to start with OpenWeather API

OpenWeather has differents API calls. You can see all the options here

We are using two of those:

• Current weather data
• One Call API

All right first things first. You are going to create a re-useful fetch function to get data form the API

The first API call (current weather data) is getting a response with the current weather for an specific city name (lets use the option By city name). The response also contains the latitude (lat) and longitude (lon) things that you will need for the next API call."

HERE'S WHAT I'VE DONE:

I'm new to Retrofit, I have an activity hosting 3 fragments for a weather app. My FirstFragment is where the current weather data will be displayed using OpenWeatherMap One call API https://openweathermap.org/api/one-call-api. I noticed that retrofit request calls cannot be made on the fragment class, so I tried using my Activity class and everything worked properly except these following lines:

I am learning react-redux. I got the following problem:

1. I make two async api calls (with redux-thunk):

• the first one to fetch country names (in one object, ex: {countries: [{...}, ...]}.

1. Those country names I use afterwards to make a second api call, to get all the soccer leagues, that are in those countrys (sometimes, there are none, so I get a null). In this case, the call is made with each countryName separatly. I make out of the results an array.
2. This arrays length is 255m out of which I filter out the null values and map the leagues names.
3. After I click on a League's name, a page is rendered ({Link} from "react-router-dom";). NOW my problem occurs
4. When I click, to get back to my home page (), both useEffect() are making an api call again. Why?

Here is the code for my useEffect():

I am trying to find 7 days weather forecast using openweather API , but when I am calling the openweather API then the data are not coming for the current location, can anyone guide me to find the correct API to get weather forecast for the current location.

API's used so far

1. I am trying to access to Dynamics 365 Field Service' fields.

I use Python, Flask to build the webapp

1. I need to CRUD Work orders : https://docs.microsoft.com/en-us/dynamics365/customer-engagement/web-api/msdyn_workorder?view=dynamics-ce-odata-9

2. I am using the multi-tenant server-to-server authentication mechanism: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/use-multi-tenant-server-server-authentication

3. I have setup the App Registration on Azure: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

4. I have configured several permissions:

• Odata.FullAccess
• AX.FullAccess
• CustomService.FullAccess
• User.Read
• User.ReadBasic.All

1. I use the code-template provided by Microsoft to build my web app interacting with Active Directory and Dynamics 365

   https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-call-api-overview

I have this code here.

I have not been able to link the Azure Active Directory access control in our ReactJS application to our API, and reading through the documentation on this matter has left me with more questions than answers.

I first began by following the instructions in the AAD Single-page app scenario, which was straightforward and allowed me to log in to my AAD account on the web, which I mentioned previously. That worked well.

However, when it came to configuring our NodeJS API, I was presented with two options: A Web app that calls web APIs, and Protected web API.

In A Web app that calls web APIs, the registration was straightforward and led me to believe that this was the way to go, however the Code Configuration page states that only ASP, Java, and Python are supported. I was unable to find any JavaScript examples for this scenario, so I moved on to Protected Web API.

Similarly, while I found the registration portion to be easy to follow, the Code Configuration page only listed examples in .NET, NodeJS (but only for App Functions, rather than a standalone API), and Python. Given that the NodeJS example was close enough to a standalone API, I followed along with that code, substituting our configuration options where appropriate, seeing as it used the passport-azure-ad package that I saw elsewhere and previously had tried to implement. However, in both cases, every attempt to make an API call against the protected endpoint resulted in the API logging the following:

“authentication failed due to: In Strategy.prototype.jwtVerify: cannot verify token”

Additionally, and I’m not sure how related this could be, but I noticed that when I decoded the ID Token and Access Token on the ReactJS application, the ID Token version was 2.0, but the Access Token was 1.0. Searching through Github Issues and StackOverflow showed that others had observed this behavior as well, although I was unable to replicate their processes in order to get a v2.0 Access Token, which I suspect but am not sure is the reason for the inability for the NodeJS API to verify the token.

Oh, and I have observed the same behavior when using MSAL.js 1.3 as well as the 2.0 beta in the client, in case that helps.

I'm trying to post a request using curl to my es cluster in AWS using my accessKey and secretKey. I have successfully done this through postman (details here) where you can specify AWS credentials but I would like to make this work with curl. Postman can auto-generate your curl request for you but all I get are errors.

This is the generated curl request along with the response