fix(connect): a Continue to Slack link, a landing page that exists and a plain refusal

Conversation 0 Commits 1 Files Changed 10

+364 -21

1 Commits

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	80bea0f931	fix(connect): a Continue to Slack link, a landing page that exists and a plain refusal maven / build (push) Successful in 1m35s Details build / maven (push) Successful in 1m35s Details Install for my organization and Connect Slack on the Connections table ended on an empty screen with only a Return button. The screen declared a view field (authorizeUrl) but no component, and a frontend step shows only the components it declares. The screen is now an HTML component: one sentence about what happens, a Continue to Slack link to the consent page (same tab, so Slack can return the browser) and the lifetime of the link, read from SlackOAuthState.LIFETIME_SECONDS (10 minutes). After Slack, the callback redirected to /preferences?section=slack, which the host UI does not serve. It returns to /app/preferences?section=slack with &result=connected or &error=<code>. Connecting in an environment without the public URL or the Slack app secrets failed with "IllegalArgumentException (Slack public URL is required)" or "Slack secret unavailable". It is refused before any state is issued with a user-facing message that says Slack is not set up in this environment, which of the two is missing, and the names of the missing environment variables, never a value. The Preferences action still answers with the authorize address as the whole message: core has no redirect field on an action result. qqq-frontend-next opens a message that is only an https address. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 06:29:49 -06:00

Author

SHA1

Message

Date

james.maesandClaude Fable 5.2

80bea0f931

fix(connect): a Continue to Slack link, a landing page that exists and a plain refusal

maven / build (push) Successful in 1m35s

Details

build / maven (push) Successful in 1m35s

Details

Install for my organization and Connect Slack on the Connections table
ended on an empty screen with only a Return button. The screen declared
a view field (authorizeUrl) but no component, and a frontend step shows
only the components it declares. The screen is now an HTML component:
one sentence about what happens, a Continue to Slack link to the consent
page (same tab, so Slack can return the browser) and the lifetime of the
link, read from SlackOAuthState.LIFETIME_SECONDS (10 minutes).

After Slack, the callback redirected to /preferences?section=slack,
which the host UI does not serve. It returns to
/app/preferences?section=slack with &result=connected or &error=<code>.

Connecting in an environment without the public URL or the Slack app
secrets failed with "IllegalArgumentException (Slack public URL is
required)" or "Slack secret unavailable". It is refused before any state
is issued with a user-facing message that says Slack is not set up in
this environment, which of the two is missing, and the names of the
missing environment variables, never a value.

The Preferences action still answers with the authorize address as the
whole message: core has no redirect field on an action result.
qqq-frontend-next opens a message that is only an https address.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

2026-11-11 06:29:49 -06:00

fix(connect): a Continue to Slack link, a landing page that exists and a plain refusal #37