Feature: Include logout endpoint in the well-known document
Description: The logout endpoint is not listed in the well-known document. This
Use-case: I am using an application development framework to build an app that uses Okta for authentication. The framework that I am using uses OpenID Connect standards to simplify the process of integrating authentication services from providers such as Okta. The success of the solution depends on providers such as Okta sticking to the OpenID standards. In this particular instance, because the logout endpoint is not mentioned in the well-known-document, it means that the app development framework cannot automatically build the logout flow for me. I will have to invest in custom coding the logout procedure. This is a simple enhancement that has a huge impact on developers who use such frameworks.