Auth Error, Error: Bad Request
See original GitHub issueQ&A (please complete the following information)
- OS: macOs
- Browser: chrome
- Version: 69
- Method of installation: npm
- Swagger-UI version: ? swagger-ui-express 3.0.1 comes with a static directory with swagger ui.
- Swagger/OpenAPI version: 2
Content & configuration
Example Swagger/OpenAPI definition:
securityDefinitions:
oauth:
type: oauth2
tokenUrl: /oauth/token
flow: application
security:
- oauth: []
Swagger-UI configuration options:
// Configure Swagger Docs
let swaggerDocument = yaml.safeLoad(fs.readFileSync('./api/swagger/swagger.yaml', 'utf8'));
app.use('/docs', swaggerUi.serve, swaggerUi.setup(swaggerDocument));
Describe the bug you’re encountering
I am no longer able to authentication through live docs. Debugging the POST request to /oauth/token via chrome devtools shows that the client_id and client_secret are not being send. grant_type is and is the correct value “client_credentials”.
To reproduce…
Steps to reproduce the behavior:
- Go to /docs (my configured router for swagger ui via express)
- Click on ‘Authenticate’
- Enter ‘client_id’
- Enter ‘client_secret’
- Click modal ‘Authenticate’ button, which submits the form
- See error
Expected behavior
Should authenticate
Screenshots
Additional context or thoughts
I know that the yaml config for OAuth2 is being consumed because its giving me the OAuth2 authentication form. The break down is in sending the entered credentials.
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Error: Bad Request when trying to authenticate user
If the external API request returns an Error: Bad Request (or any other error), the application would get that error directly as you...
Read more >Bad request 400 when trying to retrieve the Access Token
Well, that information is actually interesting -- it shows that your error is coming from the reverse proxy (nginx) that sits in front...
Read more >400 Bad Request - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request ......
Read more >OAuth HTTP error response reference | Apigee Edge
HTTP/1.1 400 Bad Request {"ErrorCode" : "invalid_request", "Error" :"Redirection URI is required"} ... "Error" :"Invalid Authorization Code"} ...
Read more >400 Bad Request when redirecting to the /authorize endpoint ...
Resolution · OIDC application may be set to INACTIVE in Okta. Make sure the application you are testing with is set to ACTIVE...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pacey, can you email me about this? I have a branch here, I’d like for you to take a look and tell me if it addresses your use case.
kyle.shockey@smartbear.com
.Thanks for the clarification here. For future readers the basic authorization header is constructed by base 64 encoded a string that contains client_id and client_secret and is delimited by “:”.