Private API parameters being shown in workflow editor?

[georgecollier]

Anyone seeing issues with private API connector parameters being shown in the workflow property editor?

Edit: just saw this, maybe related? API connector not working?

[J805]

Hmm. That is concerning. I am not seeing that issue yet. Does it also expose it to the front end potentially causing a serious security issue?

[georgecollier]

@J805

Does it also expose it to the front end potentially causing a serious security issue?

I checked that first thing, and no.

[J805]

Well, that’s good at least. Still frustrating though for sure. I see someone on slack talking about the same exact thing. So definitely report it. It must be just not pushed out to all the apps yet.

[georgecollier]

This is now fixed

[Jici]

I’ve some issue since a few days with API Connector. I guess they working on some change actually because a lot of differents issues are reported by users

[georgecollier]

Bubble had me thinking I’d left everything exposed

[tradeup]

Not fixed!

I just made a post about this on another thread.

Bubble Outage - Major

Major issue with my API connector that my entire site runs off of. I was wondering why my API calls were not working and I found out why. Certain fields from the API request were undefined and when I looked into the API call action in my workflow, I noticed that the fields I have checked as “Private” in my API call, are PUBLIC, and the ones that are not checked are the ones that are Private. [image] [image] How does this even happen? @fede.bubble Edit: This is very urgent.