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
I've been working on a project where I initially developed a login form that validates username and password against a single-sign-on server. To enhance the user experience by reducing the need for frequent logins, I stored the session.PublicKey() for automatic authentication post a successful login, as per the example in your documentation.
However, I encountered an issue where session.PublicKey() was returning empty. To resolve this, I added the following:
This change successfully allowed me to access the public key, but it introduced a new problem. Now, clients without a public key cannot connect, receiving a Permission denied (publickey) error.
Is there a way to configure the system so that I can both access the public key for users who have it, and still allow clients who don't support public keys to connect? Ideally, I want to support both types of clients without compromising the convenience of automatic authentication for those who can use public keys.
Any guidance or suggestions you can provide would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
Hello
charmbracelet/wish
team,I've been working on a project where I initially developed a login form that validates username and password against a single-sign-on server. To enhance the user experience by reducing the need for frequent logins, I stored the
session.PublicKey()
for automatic authentication post a successful login, as per the example in your documentation.However, I encountered an issue where
session.PublicKey()
was returning empty. To resolve this, I added the following:This change successfully allowed me to access the public key, but it introduced a new problem. Now, clients without a public key cannot connect, receiving a Permission denied (publickey) error.
Is there a way to configure the system so that I can both access the public key for users who have it, and still allow clients who don't support public keys to connect? Ideally, I want to support both types of clients without compromising the convenience of automatic authentication for those who can use public keys.
Any guidance or suggestions you can provide would be greatly appreciated!
The text was updated successfully, but these errors were encountered: