Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

automatically add localhost callback in sample apps or allow redirect URI to have multiple APIs or allow to edit redirect uri #143

Open
stcalica opened this issue Apr 22, 2020 · 1 comment

Comments

@stcalica
Copy link

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

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.

@ryanlink
Copy link
Contributor

ryanlink commented May 1, 2020

Thanks @stcalica - I have entered this as a feature request for tracking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants