Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How can I use client_secret for authorization?

See original GitHub issue

Hi. I want to use direct authorization (maybe Client Credentials Flow) for my application, that is, use the client_secret and application ID for authorization. How can I transfer the secret key by vk_requests? Or vk_reuqests doesn’t support this type of authorization?

Issue Analytics

State:
Created 5 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

prawn-cakecommented, Mar 24, 2019

The feature is available in v1.2.0.

0reactions

proninyaroslavcommented, Mar 10, 2019

I sent a patch that adds this feature.

Top Results From Across the Web

The Client ID and Secret - OAuth 2.0 Simplified

The client_secret is a secret known only to the application and the authorization server. It is essential the application's own password. It ...

Client Secret Authentication Methods - Cloudentity

Client secret methods are the most commonly used authentication mechanisms for regular server OAuth applications, daemons, machine-to-machine or ...

Client Credentials Flow - Auth0

The application authenticates with the Auth0 Authorization Server using its Client ID and Client Secret ( /oauth/token endpoint). Auth0 Authorization Server ...

OAuth 2.0 Authorization - Jenkov.com

At registration the client application is assigned a client ID and a client secret (password) by the authorization server. The client ID and ......

Using Client Secret with OAuth 2.0 authorization code flow

When a Resource Owner (end user) is authenticated, he gets an Authorization Code from the authorization endpoint. This code is sent to the ......