Template paths in tokenUrl parameter of security definition

I’m running into an issue with the spec.

https://github.com/swagger-api/validator-badge/issues/73

It seems that template paths are not allowed in the tokenUrl parameter of security definitions.

my use case is:

securityDefinitions:
  oauth2PasswordSecurity:
    type: oauth2
    flow: password
    tokenUrl: 'https://example.com/V2/user/{user_id}/oauth/token'

I’m not sure if it’s a bug in the 2.0 spec or a feature for next version. What would be the best way to deterministically describe template paths to clients ?

[PierreFritsch]

To formalize the implicit requirement appearing in @dkirrane’s and @anderson-marques’s comments:

For parameterizing the tokenUrl et al. in the OAuth Flow object, it would feel most natural to me to have a variables object there, which would be working like the Server Variable Object used to define the variables of the url in the Server object.

[halungge]

What is the state on this one? I think the templateing functionality really is need for multitenancy application and support of different environments both mentioned above.