We are nearly done with our cuba to jmix migration journey and just recently enabled open id. Unfortunately, with open id enabled, our consumers won’t be able to use ‘oauth/token’ flow which will retrieve the access token form them in order to subsequently invoke our api endpoints. We are forced to setup a service to service authentication with our oauth provider in order for our consumers to access our api endpoints. This is very painful and disruptive in our operations.
Is there a way to enable open id whilst keeping JMIX’s own oauth/token worfklow when accessing our own secured rest api endpoints?