So what happened is i deployed two azure web app in Azure Web App service (Frontend and Backend). Then I set-up both authenticated by Azure Active Directory.
Now, In the browser when I login via frontend, I can access both frontend and Backend. However, when I logout in frontend using '.auth/logout' I can still access the Backend?
Any idea about this ?
Related
We have created a SharePoint provider-hosted app and the Web App of the app is hosted in the Local IIS.
We are also using the App only permission with the Tenant Full control as follows:
Now, one of our clients is looking to Generate a Client ID and client secret in Azure and wants to use them in the SharePoint provider-hosted app.
Is that possible to generate without hosting the Provider hosted app in azure using the app service?
I have an internal web application (ASP.NET) that I want to expose to the internet, preferably thru Azure Application Proxy. The requirements are to use an existing external keycloak server for user authentication, the keycloak server is hosted separately from our Azure. I have read that Azure Application Proxy requires Azure AD ( not sure about this), but it is not clear if Azure AD can be connected/use an external Keycloak server.
My question is can Azure Application Proxy be made to work with an external KeyCloak service to authenticate and authorize users, or is there some other way to expose the internal web application to the internet with Azure and an external Keycloak server.
Using Azure is not a fix requirement, but it is preferred.
Using the external Keycloak server is required.
Thanks in advance for any help with this.
I deployed a sample rest web service in ACR, and later deployed to Azure App Service. Initially when I deployed the application in wildfly server, it can be access via {server-url}/{port}/home as my default sample request mapping url.
However, when I dockerized the application and push to ACR and finally deployed to Wildfly Azure App Service, I don't know how to access the /home endpoint since the App service will typically give you a default public url for your app.
Can someone help me how to access endpoints from your controller when it is deployed to App Service. Thank you in advance.
I have a app hosted in Azure. Currently when a user is authenticated in Azure AD but does not have access to the application, a generic message appears suggesting the user should request access from an administrator.
Now how would I redirect the user to a specific URL when they get this page from Azure AD ? I see no way to configure this in Azure.
EDIT
A little more technical details :
My App is hosted in a serverless Azure App Service. It is an Angular application using msal.js to authenticate.
The App is manually configured in Azure AD using Application Registration tab.
I've created a web application API with a swagger interface that I've deployed as an API App to Azure.
When creating a Logic App I can find my API App but whenever I try to use it I get the following error:
Failed to fetch swagger. Ensure you have CORS enabled on the endpoint
and are calling an HTTPS endpoint.
I'm using the default https url for the API definition in the API App:
https://microsoft-SOME-LONG-MS-INTERNAL-ID.azurewebsites.net/swagger/docs/v1
The swagger docs have been provided in my C# web API application through Swashbuckle.
For CORS I've set a single * item.
This didn't seem sufficient for the Logic App to access the API App I then configured Authentication / Authorization for the API App to use Azure Active Directory (express), creating an AD Azure App.
I believe the issue will be one of configuring security which is all pretty new to me in Azure. I'd like to make the API App inaccessible externally, but available to Web Apps and Logic Apps within my Azure subscription.
I've not added any authentication mechanism to the ASP.NET web application itself as I figured the web application would effectively be sitting in a private network on Azure. Perhaps this is a bad assumption and I need to add authentication to allow Azure AD to work?
Any pointers / suggestions?
Turns out I needed to update the Azure SDK for Visual Studio. I had an older version that was deploying a preview Api App which resulted in a "Api app host" type being deployed rather that an "API app" type.
Everything works after the update and I've found some documentation for securing the API App and making it available in the Logic App - https://azure.microsoft.com/en-us/documentation/articles/app-service-logic-custom-hosted-api/