You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm having two Solo2 (One is a Typ-C and the other is Typ-A), both of them are the hacker version and on the latest firmware.
I'm having a really strange behavior (which is different on both devices).
Let me first explain what I did.
I plaid a little bit around and figured out that Firefox is not supporting CTAP2 (which is necessary for setting up a pin and prefill the username).
So I went into Chromium and added a pin to my (Typ-A) solo2. After that, I used my Authentik Instance where I added the key with WebAuthn (CTAP2).
Everything went fine...
But a little bit later, I went into Chromium, into the chrome://settings/securityKeys settings page and clicked on Sign-in Data which shows all WebAuthn connections.
So I saw my connected Authentik instance.
And then I saw that the LED is blinking in a different color.
So my Typ-A and Typ-C are fading green (in idle state), but when I start a connection (for example authenticate and stuff like that), the Typ-A is now blinking green/orange.
Typ-C is blinking green (which is the default behavior and was the same behavior all the time).
So, it's really weird that both devices, which are the same, has different behaviors.
The "untouched" Typ-C (which I just used in Firefox with CTAP1) are only showing a green light (fading, blinking, flashing etc.).
But the Typ-A (which I just added in Chromium and removed) is blinking and flashing between green and orange, just the idle fading is green.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm having two Solo2 (One is a Typ-C and the other is Typ-A), both of them are the hacker version and on the latest firmware.
I'm having a really strange behavior (which is different on both devices).
Let me first explain what I did.
I plaid a little bit around and figured out that Firefox is not supporting CTAP2 (which is necessary for setting up a pin and prefill the username).
So I went into Chromium and added a pin to my (Typ-A) solo2. After that, I used my Authentik Instance where I added the key with WebAuthn (CTAP2).
Everything went fine...
But a little bit later, I went into Chromium, into the
chrome://settings/securityKeys
settings page and clicked onSign-in Data
which shows all WebAuthn connections.So I saw my connected Authentik instance.
And then I saw that the LED is blinking in a different color.
So my Typ-A and Typ-C are fading green (in idle state), but when I start a connection (for example authenticate and stuff like that), the Typ-A is now blinking green/orange.
Typ-C is blinking green (which is the default behavior and was the same behavior all the time).
So, it's really weird that both devices, which are the same, has different behaviors.
The "untouched" Typ-C (which I just used in Firefox with CTAP1) are only showing a green light (fading, blinking, flashing etc.).
But the Typ-A (which I just added in Chromium and removed) is blinking and flashing between green and orange, just the idle fading is green.
I hope I explained it well enough... ^^"
Beta Was this translation helpful? Give feedback.
All reactions