Keep JMIX's own oauth/token flow when enabling open id

Support
#1

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?

#3

Hi,

There is a section in the OIDC add-in README file that demonstrates how you can get access token and use it for protecting an API. Could you please explain why it doesn’t work for you?

#4

So this section of the readme file just contains added configuration but still forces us to use the external auth provider for retrieving tokens to be used for calling api. It’s not that it’s not working, it’s just that in our organisation, a different group manages our azure ad and it’s just a pain when it comes to coordination (different time zone and each request you have to wait a day to accomplish). What we’re actually thinking is that if we can use the local oauth/token for a while and be able to use the token provided to call the api endpoints, while we sort out the configuration in our azure ad.