Is your feature request related to a problem? Please describe.
Right now it is not possible to use the try-it-out functionality for authenticated developers in a portal. This is because it is assumed that the clientid/secret will be different, so it is asked to the developer again.
We believe it is a common use case and a good feature for authenticated developers to have direct access to the try-it-out functionality.
Describe the solution you'd like
I would like to login in a Portal as a developer, using Oauth, and then being able to use the try-it-out functionality:
reusing the clientId + ClientSecret defined under docsEnvironment > parameters > usagePlans > authPolicy > oauth > introspectionValidation > {clientId + clientSecretRef}
Describe alternatives you've considered
It is assumed that this will only work if the api has an Oauth usage plan defined, and the user is authenticated
Additional context
The issue we have with the current configuration is that if we invite a developer to enter a client id and secret, he will use his application credentials and this will not work because the client id he will enter is not configured with Gloo redirect_uri
affected by https://github.com/solo-io/dev-portal/issues/2097
Is your feature request related to a problem? Please describe. Right now it is not possible to use the try-it-out functionality for authenticated developers in a portal. This is because it is assumed that the clientid/secret will be different, so it is asked to the developer again.
We believe it is a common use case and a good feature for authenticated developers to have direct access to the try-it-out functionality.
Describe the solution you'd like I would like to login in a Portal as a developer, using Oauth, and then being able to use the try-it-out functionality:
reusing the
clientId + ClientSecret
defined under docsEnvironment > parameters > usagePlans > authPolicy > oauth > introspectionValidation > {clientId + clientSecretRef}
Describe alternatives you've considered It is assumed that this will only work if the api has an Oauth usage plan defined, and the user is authenticated
Additional context The issue we have with the current configuration is that if we invite a developer to enter a client id and secret, he will use his application credentials and this will not work because the client id he will enter is not configured with Gloo redirect_uri affected by https://github.com/solo-io/dev-portal/issues/2097