Pre-existing ex_app resource doesn't seem to work

[marcelklehr]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Install exapp
2. Setup a flow with a script that uses AppAPi auth from the resource
3. Nextcloud complains that user flow_app cannot be found

Expected behaviour

App API auth should work

Actual behaviour

Auth fails

Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.1/8.2/8.3

Nextcloud version: 30, master

[bigcat88]

Cannot reproduce this.

For test a take script example from here:

https://raw.githubusercontent.com/nextcloud/flow_scripts/refs/heads/main/actions/List_calendars.py

Pressed +Resource button, changed the script to use resource from import:

The request is send fine to the Nextсloud instance.

From what I modified, I manually added nextcloud_url to the resource so that it would point to the NC in my dev setup.

So the question is, should I add the initialization of "nextcloud_url" or "baseUrl" (I don't care about the name, but we have the previous variables in Snake Case) - when initializing Windmill?

Or any other ideas? I remember we originally required admins to manually fill in baseUrl when we released the first version of Windmill, but for some reason I can't find where to edit it in the Windmill UI now, and it's not in the documentation (or I'm blind and tired):

https://docs.nextcloud.com/server/latest/admin_manual/windmill_workflows/index.html

cc @julien-nc @marcelklehr

[marcelklehr]

So the question is, should I add the initialization of "nextcloud_url" or "baseUrl" (I don't care about the name, but we have the previous variables in Snake Case) - when initializing Windmill?

Yeah, that would be good