Firstyear

Part of the reason to split it to a separate repo is so that we can delegate privileges to the arch maintainers without granting the same rights in the main...

Reopening until we open the repo for you and assign the needed privs. Who are the arch maintainers that will need access?

It is expected behaviour, but I think we may be missing the documentation for it in https://kanidm.github.io/kanidm/stable/integrations/oauth2.html#create-the-kanidm-configuration If you add a claim called groups, we will indeed add all the...

@alexvonme I think this is a docs issue you might be able to look at :)

If you add the scope groups, you will get all groups. We don't know what ones are relevant or not. If you want to limit what groups are shown, use...

Can you give an example of the json that causes the failure?

Worth pointing out that cred_props doesn't actually mean anything - it's just your browser saying if it thinks a resident key was made. It is not a true representation of...

But it's not what webauthn expects so you have to rename it. Isn't webauthn such a lovely hot mess of a specification :)

The spec is a mess. https://www.w3.org/TR/webauthn-2/#iface-pkcredential https://www.w3.org/TR/webauthn-2/#sctn-registering-a-new-credential Re-reading there is no defined name for what "extensions" should be called, just "Let clientExtensionResults be the result of calling credential.[getClientExtensionResults()](https://www.w3.org/TR/webauthn-2/#dom-publickeycredential-getclientextensionresults)." But to...

https://github.com/w3c/webauthn/issues/2275 Raised issue with wg.