storyden

Respect mah authoratah Storyden is now a OAuth2 and OIDC compliant auth server! You can also properly reset passwords while running a non-email account. Groundbreaking.

OAuth OIDC PKCE and other acronyms

We've had a few users reach out saying something like "I have a few related sites, Storyden is one of them, how do I make them all share the same login?" OAuth clients such as "Login with X" is one approach, this is called federated identity, or "SSO", or more casually, "social login". But if you want to run your own auth service, it's a lot of work to implement or even host something like Keycloak and integrate it with your sites.

Storyden can now be the central authentication service, and your other systems can "Login with Storyden". Currently we support device flow and code flow as well as PKCE.

PKCE is also a big one as it means you can more easily build mobile auth on top of Storyden using secure web-view based login.

And this is also a huge step towards...

Storyden in the terminal!

This isn't fully released and installable easily yet but it's worth calling out. More details soon but, Storyden now has an official command line app allowing you (or LLM agents!) interact with your Storyden instance(s) from the terminal.

The move here is also to make it super easy for agents to securely and safely interact with Storyden. We've taken it for quite a test drive and gotten both Claude, Codex and Grok to:

• Organise library pages, put them in the right directories and give them tags, content, images, properties, etc.
• Review/reject submissions from members for items in our library pages
• Develop, test and install Storyden plugins

We've put a bunch of thought into making the CLI self-documenting for both humans and robots:

And I mentioned security, there's a lot of attacks going around and while Storyden might not be popular enough to warrant a script reading from %APPDATA%/storyden/config.yaml we decided it would be worth not simply storing credentials in a plain text file like a silly billy. Instead we use the platform's credential store (Credential Manager on Windows, Keyring on Mac) if available, which makes it a little harder for sneaky scripts and rogue robots to get access:

And the coolest part, your favourite coding agent can put together a Storyden plugin in minutes, test it against a live instance, package it up and install it directly!

We're brainstorming new things to add to sd and it'll be released officially with Winget, Scoop, Brew, etc. soon!

For now, you can try it out by compiling the unstable in-development version from source using Go:

go install github.com/Southclaws/storyden/cmd/sd@main

Just be careful using this against a live instance, use backups, etc.

Password reset

Yes this is an absolute basic we missed for so long. Previously, if you had an instance of Storyden that did not have email enabled (username-only registration/login) it was basically impossible to reset members' passwords.

No more. You can now reset members' passwords if you hold the MANAGE_ACCOUNTS permission. If the instance has emails enabled, it'll just send the regular password reset email.

If there's no email sending capability, that's fine, you'll get a magic link to copy and send to the member however you want. This link will allow the member to reset their own password.

Cleanup

We also removed Weaviate support, I don't think anybody was using it. If you were... sorry 😬

Full Changelog: https://github.com/Southclaws/storyden/compare/v1.26.8...v1.26.9