Which connector?: Younium

Additional details:

We use Younium’s managed EU environment (e.g. web login at https://eu.younium.com/ with SSO enabled for our organization. The Younium connector today only supports username and password (and the same via the dashboard / Connect Card) against Younium’s identity configuration, per the public setup guide.

That creates a hard blocker for us:

• Human access is SSO-first; integration access should not depend on a shared or non-SSO “legacy” password user where our security policy and Younium’s own direction conflict with that pattern.
• Younium’s documentation describes modern API authentication using client credentials (Personal Tokens) and JWT, and they are sunsetting legacy username/password API authentication (public KB: deprecation 31 May 2026).
• We worked with Younium Support (legacy/integration user guidance) and still hit OAuth/SSO behavior at login; server-side sync should not require maintaining a parallel password identity that may not be allowed or may not work reliably under domain-claimed SSO.

Requested capability

Support non–password-based authentication for the Younium connector that works with SSO-backed and security-policy-compliant tenants—for example:

• OAuth 2.0 / OIDC authorization suitable for connector or service use (browser or admin-consented where required), and/or
• Client ID + client secret (machine credentials) consistent with Younium’s current developer documentation, with token refresh handled by Fivetran,

while preserving existing legal entity, environment, and API region configuration.

Outcome

We can run the Younium → Snowflake pipeline on Fivetran without exceptions to our SSO-only or no long-lived shared passwords standards, and without relying on auth that Younium is phasing out.