erebion

joined 2 years ago
sorted by: new top controversial old
Authentik: Allowing users to create invites? in c/selfhosted@lemmy.world
[–] erebion@lemmy.sdf.org 1 points 3 months ago* (last edited 3 months ago)

I already have an invite flow that users will arrive at and go through when signing up, now I want to let users create invites for other users. That page does not mention anything about that. It seems to be about adding a flow that asks user for details such as an email address and then they get their account.

In my case users have already gone through that and want to invite someone else.

With invitations, you can either email an enrollment invitation URL to one or more specific recipients with pre-defined credentials, or you can email a URL to users, who can then log in and define their own credentials.

I already have enrollment invitation URLs. Just not automatically. I wrote a script that uses the API for that purpose.

The docs even mention this about the flow:

Enrollment (2 Stage)

Flow: right-click here and save the file.

Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.

Authentik: Allowing users to create invites? in c/selfhosted@lemmy.world
[–] erebion@lemmy.sdf.org 0 points 3 months ago* (last edited 3 months ago) (2 children)

Nope. Not what the question is about. This requires an admin user to create an invitation in the admin backend. I want a way to let users do that.

16
Authentik: Allowing users to create invites? (lemmy.sdf.org)
 

Hey there,

I'd like to allow users in a specific group (not the admin group) to create invites for Authentik, so that people at my hackerspace can invite others to our Single Sign-On system.

Has anyone got a recommendation or idea how this could be done?

We also have a Nextcloud instance, maybe there's a simple tool that allows Nextcloud users to trigger an API call without revealing any API secret?

All we need is an input field that forces users to note who the invite is for and a button that allows creating it and receiving a link.

What Apps Are Missing on Mobile Linux? in c/linuxphones@lemmy.ml
2
Follow-up Two: Mobian on the Pixel 3a / 3a XL (europe.pub)
 

This is a follow-up to my earlier posts:

https://lemmy.sdf.org/post/12809764 https://lemmy.sdf.org/post/19600671

We're Getting Closer.

It's just small stuff left that needs a bit of piecing together, though I've now been daily driving my port for the past two weeks already.

This Works

  • booting
  • display
  • touch
  • modem <- You might have to switch to the other slot if it does not work: mmcli -m 0 --set-primary-sim-slot=1, options are 1 or 2. Note that the modem could also be a different number, maybe try -m 1 if it is not found as the command will reboot the modem and then it changes.
  • plymouth
  • battery/charging
  • mobile data
  • wifi
  • torch
  • suspend
  • call audio
  • vibration
  • Bluetooth™
  • full disk encryption
  • eSIM (I'm working on the packaging for the tool you need to provision it)
  • SMS
  • audio (ALSA config not packaged, but can be added manually)
  • camera (have taken a few photos, but the kernel driver is still work in progress and sometimes it just does not work)

This Has An Unknown Status

  • Fingerprint Sensor
  • NFC (should work, does so on pmOS)

This Does Not Work Yet (Soon™)

  • GPS
  • USB host mode (no Kernel support yet, but apparently this is being worked on)
  • Verified Boot (first need to do research whether this is actually feasible)

This Is Missing And Will Come Later

  • accelerometer
  • magnetometer
  • ambient light sensor
  • barometer

Project Status

To Do List

Done List

Misc Issues

  • ALSA config for the device has not been upstreamed yet
  • Issues with 5 GHz wifi
    • Can be worked around by forcing the phone to only use the 2.4 GHz band, for example using nmtui, the network settings of GNOME/Phosh are bit too simplistic for that
  • No idea how to get the call audio on Bluetooth, meaning you will have to hold the phone or use a cable, for now

(This is a non-exhaustive list)

Low Priority

Other than that... Everything should be there. It's definitely usable already.

Just a few smaller quirks to iron out and two packages to get into the repo.

The Sources (Use The Source, Luke)

Thanks For All The Fish

Huge thanks to be sdm670-linux project and flamingradian who runs the project (just one person!) to make sure the Kernel works on those devices! :)

I don’t know how Kernel development works, so I would have never started porting without this project.

Find that here: https://gitlab.com/sdm670-mainline/linux

Questions Accepted / Ask Me Anything About The Project

I will gladly answer all questions, I hope that more people will start porting if it becomes clear that this is not arcane magic. It’s mostly just arcane. And a community of friendly people that try to be helpful.#

1
KDE Kasts on Phosh: Icons missing, what's the fix? (lemmy.sdf.org)
 

Hey there,

I installed Kasts from KDE on Phosh, all the icons are missing and it therefore is difficiult to use.

How can this be fixed? Do I have to install some sort of icon package?

Maybe someone even knows the exact Debian package that's missing. :D

1
Current state of re-locking bootloaders on former Android devices? (lemmy.sdf.org)
 

Hello internet,

what is the current state of re-locking bootloaders on devices that previously ran Android?

Any implementations? How does that work?

2
Got Mobian (almost) ported to Pixel 3a / 3a XL (europe.pub)
 

Most parts work, still not sure why Bluetooth gives me errors in dmesg, audio out works, microphone input not yet... I'm getting there.

But graphics, charging, low standby power consumption, LTE, wifi... those all work already.

The fact that postmarketOS has support and also that there are people working on mainline support, makes this a task that is not as difficult as I thought, as most work was already done for another distro.

Otherwise it runs more fluid than Android ever did on it and it has a great standby time (forgot to turn it off at around 80 % and a few days later it was at 58 %).

For now stuck on merging the Kernel patches from the sdm670-mainline project with those from Mobian, not really something I can do without knowing C. I just hope someone with the right skills does it at some point.

Then I just need to make some smaller merge requests, like one to add a udev rule for vibration support and so on.

Not much missing before I can finally use it as a daily driver.