Firstyear

https://en.opensuse.org/Portal:SELinux It appears that the upstream reference policy is merged frequently, so it could also be worth submitting kanidm policy into that too. If you do open an issue per...

Is this still a problem?

Went through the claims, here are my thoughts. | Claim| Comment | |----|-----| | sub | supported | | name | supported | | given_name | can't support | |...

> Seeing as this is something I also need, I could help implementing these (I especially need profile pictures). There is more ground work than just exposing that attribute though,...

> [@Firstyear](https://github.com/Firstyear) By cannot support you're referring to the [developer ethics](https://kanidm.github.io/kanidm/stable/developers/developer_ethics.html?highlight=legalname#free-from-harmful-discrimination-of-any-kind) chapter? Yes, we don't store firstname/lastname due to cultural names existing and we want to respect those. > >...

> There's a few phone number validators, this one looks useful https://crates.io/crates/phonelib Yeah. I'm just hesitant to bring in more deps is all

Like we also could just go much simpler and use `^\+[0-9]?()[0-9](\s|\S)(\d[0-9]{9})$` which will allow e164 formatted numbers. I think we just need something that is "less strict" here, we shouldn't...

> > There is more ground work than just exposing that attribute though, profile pics are one of the harder options. > > Given that most of the back-end is...

> If no one opposes, i would cover that and use it as my personal testing balloon for my first contribution on this project. > I have already implemented the...

And as a tip @karatemuffin I'd say do "updated_at" first, it'll be the easiest one to get you familiar with how things work.