Svelte-kit and Keycloak OIDC

There’s NextAuth.js from vercel, which was made for next.js Recently it was adapted for svelte-kit. The announcement post: https://vercel.com/blog/announcing-sveltekit-auth The keycloak provider doc: https://next-auth.js.org/providers/keycloak The example repository: https://github.com/nextauthjs/sveltekit-auth-example Well it does work, on first sight. Sign in, Sign out, requiring auth for pages, it all works. However you need a confidential client. And this token…

Read Article

archlinux: pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Upgrade only openssl to version 3 from 1.1.1 and you receive this error. sudo doesn’t work, pacman doesn’t work, what do you do? Well hopefully you have not deleted previously downloaded packages from /var/cache/pacman/pkg/ . If not, read about the Arch Linux Archive and you will need a USB drive/stick/whatever with an archiso written on…

Read Article

nginx: [emerg] unknown “tls1_3_early_data” variable

If you’re getting this error message doing nginx -t or otherwise, for instance if you’re copy/pasting Mattermost’s nginx configuration, know that the line is

instead of

I’m not sure but I’m guessing nginx developers renamed that variable, I’m just not sure when that happened. $tls1_3_early_data must have worked some time ago, but on…

Read Article

Keycloak Client Passwords are insecure by default

And the maintainers refuse to change that, responding with bureaucratic measures and general ignorance. When you have an UUID string, example “192c1916-de80-4003-a01b-b2eaf97a1721” first of all those aren’t 128 bits. You have a representation of those 128 bits and a very limited set of characters 0123456789abcdef, so you represent those 128 bits in only 16 characters…

Read Article