I’m attempting to put together a simple identity server following the directions here: http://docs.identityserver.io/en/latest/ , and the project runs locally fine, I have only created a new project, not made any modifications. Running locally it launches, and I can load the .well-known/openid-configuration endpoint with no issues.
I take this bare bones project and attempt to upload it to an azure webapp and get the attached:
HTTP Error 502.5 - Process Failure
It appears that the application fails to start in azure.
I can publish a .NET Core MVC application no problem, but with this IS4 template I always receive the process failure. What am I missing? Should this not work out of the box here?
The other answer is incorrect and insecure. That default code is there for a reason. During development you have a developer signing credential, for production you have to implement your own signing credential. See the following answer:
How do I configure "key material" in Identity Server 4 to use SQL, KeyVault, or any other system?