Skip to content

OIDC/SSO moves to PLANKA Pro with the next release #1754

Description

@daniel-hiller

OIDC/SSO moves to PLANKA Pro with the next release

Hi everyone,

first of all — we're back. Things went quiet here over the summer, and we
appreciate your patience during the break. We're picking development back up,
and the next release comes with a few changes worth explaining.

The main one: with the next release, we're removing OIDC/SSO from the Community
version — from then on it'll only be part of PLANKA Pro.

Why: SSO was always meant to be a Pro/enterprise feature on our side. The fact
that it ended up in Community never fit that model, and we're straightening
that out now.

On top of that, honestly: SSO is by far the feature that costs us the most
support — over 100 setup requests a month, docs or no docs. And as our
[License Guide] already says, direct support is for Pro/Enterprise anyway. So
that's simply where SSO belongs, where we can maintain it properly.

We're also using this release to move account security in the other direction.
Several features that used to be Pro are now part of Community:

  • TOTP-based two-factor authentication
  • Auto-logout after inactivity
  • Trusted devices (skip 2FA for a set period)

Our line is simple — account security stays free and open, enterprise identity
management (SSO) is Pro.

What changes

  • Starting with version 2.2.0, PLANKA Community no longer includes OIDC/SSO.
  • Login via username/email and password stays in Community.
  • TOTP 2FA, auto-logout, and trusted devices are now available in Community.
  • Older releases stay available and keep working — we don't disable anything
    remotely. But updating to 2.2.0 removes OIDC/SSO.
  • If you need SSO, you can move to PLANKA Pro, where it's included and
    supported: https://planka.app/pro
  • Migrating from Community to Pro is possible; migration is available in the
    customer panel after purchase.

⚠️ Important before you update
After updating to 2.2.0, all SSO-based users are deactivated, since they no
longer have a password login. To restore access, an admin can set a password
for each affected user and reactivate them.

If your admin account itself is SSO-based, you'll be locked out — in that
case, create a new admin user first (via script or environment variables) as
described here:
https://docs.planka.cloud/docs/configuration/admin-user

If SSO is critical for your team, plan this migration before you update.

We know this affects some of you, and we're not doing it lightly. Getting the
tiering right now is what keeps PLANKA sustainable long-term. Nothing changes
about the license itself:
Community License
·
License Guide

Thanks for sticking with us — questions welcome in this thread.

— The PLANKA team

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions