Firstyear
Firstyear
Ahh it looks like to_json is a helper from various browsers, and doesn't seem to be in webauthn L2 - it's part of the editors draft: https://w3c.github.io/webauthn/#typedefdef-publickeycredentialjson That's why we...
This is a good suggestion, but it requires us to handle some new states in our authentication handlers that we currently can't. It's similar to #3218 The tl;dr is our...
If the user changes their mind and wants a different type of credential then we need to step back. That's the issue.
we have to submit the request to actually render the next prompt because when you pick a "mech" it returns with details like *challenges* that are needed for the request...
Okay, and now if you don't want to use that mechanism? you have to go back. So the issue is the backward step, not the forward.
> So we need to support that option in the state machine, a different problem to [#3328 (comment)](https://github.com/kanidm/kanidm/issues/3328#issuecomment-2574438713) No, it's the same - if you hit the browser back button...
We have other priorities at this time. We appreciate your interest in the feature though.
When you initialise the auth session, the X-KANIDM-AUTH-SESSION-ID is returned to you in both: * The header X-KANIDM-AUTH-SESSION-ID * In a cookie with the key "auth-session-id" In both cases the...
> First, from previous discussions, I'll add two things: > > 1. The enumeration problem is a bit worse than just users, the anonymous account can by default also enumerate...
anonymous is *technically* an account though.