While deploying keycloak image to azure appservice, I would like to change this "http://localhost:8080/auth" to something https://appservicekeycloak.azurewebsites.net/auth/.
Not sure how it can be configured.
Related
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 an AD FS server in a VM in Azure for test purpose. It is not for production and some downtime does not matter.
However it should be available on the Internet for SSO.
Can Azure App Gateway be used for protection of AD FS?
Or is the Web Application Proxy server required?
If I setup a WAP server should it be protected by App Gateway and WAF?
WAP is recommended. No need to deploy WAF or Azure App gateways.
See https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs for deployment guidance.
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 ?
I am hosting an MVC web application in Azure App Service with Azure AD synching with our on prem AD. I need the app pool to run under a specific account so I can access our on prem SQL Server (via trusted connection). Can anyone point me in the right direction?
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/