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

configuring OAuth for 3.x #2897

Closed
fehguy opened this issue Apr 11, 2017 · 2 comments · Fixed by #3074
Closed

configuring OAuth for 3.x #2897

fehguy opened this issue Apr 11, 2017 · 2 comments · Fixed by #3074

Comments

@fehguy
Copy link
Contributor

fehguy commented Apr 11, 2017

Previously we could configure the oauth client id, client secret, realm, appname, scope separator in the index.html. This made sense, since these would typically be static for a single API, and swagger-ui would render the UI specifically for it.

It's not clear how this is done with swagger-ui 3.x. We want to have a way to configure the above values as the end user will really have no idea what they are, nor should they have any business messing with them.

I'd like to see a way to configure them in the index.html like before, and have it documented in the README.md. This is a high priority because until they're in here documented, the OAuth support is almost useless.

@banejasika
Copy link

Any update on this?

@lock
Copy link

lock bot commented Jul 2, 2019

Locking due to inactivity.

This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.

If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.

Thanks!

@lock lock bot unassigned bodnia Jul 2, 2019
@lock lock bot locked and limited conversation to collaborators Jul 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants