PipedreamHQ / PipedreamHQ/pipedream
[BUG] Submit an app form doesn't let capture session auth configs smoothly
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Describe the bug**
When you want to submit an app having Session Auth as authentication method, you have to use the layout for OAuth. While the requests displayed in OAuth authentication method are enough to handle Session Auth, it is necessary to tweak the different requests configs, in order to make the Session Auth flow using the layout for OAuth.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to the 'submit an app form' https://pipedream.com/submit-an-app
2. Fill 'Basic Info' tab, then hit 'Save'
4. Go to 'Authentication Strategy' tab
5. For 'Select an auth type', select 'OAuth', then hit 'Save'
6. Setup 'Request Token request'
7. Setup 'Test request',, then hit 'Save'
8. Hit the 'test' button
9. log pop up show 'no host component for URI'
**Expected behavior**
the test request is executed properly. the submit an app form is able to detect that OAuth ID/Secret were set to "DO NOT USE" and recognize no setup (ie. URIs) are necessary under Authorization/Access Token/Refresh token requests
the token from 'Request Token request' should be propagated via custom, oauth, or any other variable bag and be available in 'test request' to reuse
or
create a new authentication method for Session Auth
**Screenshots**
If you setup 'Request Token request' and 'test request', which appears to be enough for a Session Auth based application, you get an error 'no host component for URI' , here is the setup:

here is the error, down in the bottom

**Additional context**
this is a recurring issue when tackling session auth apps in the submit an app store project.
for an example of the workarounds, see the following setup, where 'Request Token request', 'Access Token request', and 'Test request' are setup, and values from "token" are extracted from 'Request Token request' and propagated to 'Test request' via extractin a custom field "access_token" of 'Access Token request' as a middle man.
setup part 1) oauth client setup and request token request

setup part 2) access token request and test request

the "access token request" shouldn't be necessary to setup for a Session Auth app
Contributor guide
Assessment
This issue has not been assessed yet.