For quick testing, I call the JWT api in postman to make sure i am talking to everything correctly. In postman setup the header with the content type of application/json, and the body contains the json string with the username and password
When it works, it sends back a token. I'm running it against docker desktop, IIS (azure vm server not local), azure container instance, azure container app. When the jwt works, the powerserver application will work. (if the JWT is not set to enabled/required, then any of the other powerserver api's can be called instead for testing)
With IIS i can setup different ports and call it with HTTPS.
With docker (local) instance, i can setup different ports (5009 etc.) and it works, but only if call it with HTTP. https does not work. for docker the api call is: http://localhost:5009/connect/token
with container instances, they can easily setup containers with different ports, but only 80 works with http. Once an container instance is setup, you can not change the port. you have to delete and recreate it.
container app fails in the deploy.
https is what i need to use to connect for security. I can get that to work with IIS only.
most (all?) examples that are provided use http and not https.
I found an Azure Container Instances guide that shows how to create a container group with an application container and a sidecar container running a TLS/SSL provider. By setting up a container group with a separate TLS endpoint, you enable TLS connections for your application without changing your application code.
Refer to: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-ssl
it seems easier to maintain TLS in the sidecar container if you don't want to upgrade all of the application containers just because a certification expires.
Regards, Logan
The authentication may move me to instance instead of app container however. I was planning on using built in JWT with some custom validations, but the container app seems to clear the token cache. or i could use external service i suppose.
Looking into the scale requirements as well to allow it to scale to zero in order to save money when its not in use. The cost is pretty low in any case (35/month to run full time, but probably about 1/2 that if it is setup to scale to 0 ). The scale to zero option is really compelling for a testing server since it should scale to zero most days. The https cert is included with the container app, so depending on what you are doing it can be very cost effective.