-
Notifications
You must be signed in to change notification settings - Fork 0
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
research how to use typeform answer API with ktor client #15
Comments
ktor will request data from typeform. Authentication should happen once, the token stored to do multiple requests on typeform. |
Sould we use webhooks to call our platform? I see that the webhook calls contain the form submission data. The data is protected by https, and validated with an encrypted value one should decrypt on the server side to make sure it comes from Typeform. The data itself is not encrypted (except for https). Delivery is retried 5 times at increasing intervals. https://developer.typeform.com/webhooks/ If I understand it right webhooks are a non-free option. |
I made a form for testing: https://x7dxsyy4g0y.typeform.com/to/fBwJApPU https://developer.typeform.com/get-started/ |
https://www.scottbrady91.com/kotlin/ktor-using-oauth-2-and-identityserver4 Ktor OAuth Support Currently, Ktor only supports OAuth which means our Ktor application can receive access tokens to talk to an API on behalf of the user, but it cannot find out who the user is. If we wanted to find out who the user is and to receive identity tokens, we would need OpenID Connect, which is currently unsupported. The Ktor OAuth library is hard-coded to support the authorization code flow. Ideally, in this scenario, we’d also like to use PKCE so that we can prevent authorization codes from other users being injected into our application. Also, due to an oddity in the OAuth 2.0 specification, the Ktor basic authentication mechanism may not work with some authorization servers (basic auth is usually base64(client_id + ":" + client_secret) but OAuth defines it as base64(urlformencode(client_id) + ":" + urlformencode(client_secret)). Only the query string response mode is supported, and the default value for state is random, utilizing a nonce (no more than once) generator. |
https://github.com/mazine/oauth2-client-kotlin#client-flow- Note: not updated in 6 years Client FlowUse it if
For further details check OAuth 2.0 Spec The library allows to create an
|
Now I see there's a solution partially implemented already in the code. |
establishing proper, transparent oauth2 support in ktor.
The text was updated successfully, but these errors were encountered: