REST API Datasource fails to persist Bearer Token | Appsmith | Page 1

fluid sphinx Jun 10, 2023, 1:35 PM

#

Hello,

I'm trying to set up a REST API Datasource with Bearer Token auth. However, when trying to use a query with this datasource, I receive an error message:

<Name of my Data Source> is not correctly configured. Please fix the following and then re-run: [Secret key is required when sending session is switched on, and should be at least 32 characters long., Secret key is required when sending session details is switched on, and should be at least 32 characters in length.]

I've tried setting a 32 character token in the Datasource, the key is saved successfully.

However after trying to use the source in a query, the error I mentioned above appears in the console.

I reopen the Data Source and the key is missing.

I believe there's some kind of validation missing from the edit Datasource view in AppSmith and it's rejecting my token.

frosty flareBOT Jun 10, 2023, 1:40 PM

#

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Pranav

serene cloud Jun 10, 2023, 4:34 PM

#

Hi @fluid sphinx

I reopen the Data Source and the key is missing.
This is the expected behavior for all encrypted fields. The credentials save to the Appsmith server (our cloud, or your self-hosted instance), and never get transmitted back to clients again- not even in the editor, for admins. When you edit a datasource, you have to re-enter all encrypted fields.

What API are you integrating with? Could you show a screenshot of the datasource configuration, without the key? Feel free to DM me if you prefer.

fluid sphinx Jun 10, 2023, 5:27 PM

#

Thanks Joesph, I’m integrating with my own apps API. I’ll send a short screencast later showing the behavior. The feedback from the query console shared above is making me think that the bearer token secret is never saved.

frosty flareBOT Jun 12, 2023, 3:26 PM

#

@fluid sphinx Gentle reminder.

fluid sphinx Jun 12, 2023, 3:44 PM

#

Here's a screen recording, and I actually found the issue while rubber ducking:

https://share.cleanshot.com/fl7x3nky

CleanShot 2023-06-12 at 11.39.37

Video uploaded to CleanShot Cloud

#

Long story short, the Data Source edit/create form doesn't validate the precence of the AppSmith Signature header if you have enabled that setting.

The error message in the console says "Secret key is missing" but I didn't realize that the Signature header was the secret key, I thought it was the Bearer token.

frosty flareBOT Jun 12, 2023, 4:20 PM

#

Thanks for the update! I'm glad you were unblocked here. Let us know if you need
anything else.

Thank you for your support and patience. We believe your issue has been
resolved.

Please take a moment to provide feedback on our service.
https://survey.frontapp.com/v2/09a400bf433bc9676d67/96e72801705d10718ee89752513f70db

fluid sphinx Jun 14, 2023, 2:35 PM

#

@serene cloud just making sure you see this. I see bot interaction but no feedback that this is a UX bug.

#REST API Datasource fails to persist Bearer Token