You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to use the sample APIs without creating an additional request tied to the same email. This makes it confusing for the user. As well as not easy to get your example APIs in your repo to work out of the box.
Value provided by feature
It allows users to not have to request new credentials when a domain is changed or when testing.
It allows users with more complicated apps to have multiple redirect URIs tied to the same keys.
I can see the need for different credentials for testing and production but some complicated apps may now have to keep credentials and URIs tied. Or multiple testing credentials may be needed to run your samples and then a new pair for our own testing which can be annoying and creates a frustrating user experience.
Acceptance criteria
More complicated but nice would be a user dashboard with the ability to add or remove or edit our redirect URI (could regenerate new credentials when changes are made which are still emailed out).
Or automatically allow
localhost:8080/auth/cb
since this is the callback you use in your own samples and the same callback can be used by users testing their own application. This would possibly be the simplest implementation than a whole dashboard.
The text was updated successfully, but these errors were encountered:
VA Lighthouse API Feature Request
APIs affected (if applicable)
All APIs
Explanation
I would like to be able to use the sample APIs without creating an additional request tied to the same email. This makes it confusing for the user. As well as not easy to get your example APIs in your repo to work out of the box.
Value provided by feature
It allows users to not have to request new credentials when a domain is changed or when testing.
It allows users with more complicated apps to have multiple redirect URIs tied to the same keys.
I can see the need for different credentials for testing and production but some complicated apps may now have to keep credentials and URIs tied. Or multiple testing credentials may be needed to run your samples and then a new pair for our own testing which can be annoying and creates a frustrating user experience.
Acceptance criteria
More complicated but nice would be a user dashboard with the ability to add or remove or edit our redirect URI (could regenerate new credentials when changes are made which are still emailed out).
Or automatically allow
since this is the callback you use in your own samples and the same callback can be used by users testing their own application. This would possibly be the simplest implementation than a whole dashboard.
The text was updated successfully, but these errors were encountered: