We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support ssh certificates
This way users can get access without uploading a public ssh key, instead they are verified against a ssh CA.
This will need extra sshd configuration like this
AuthorizedPrincipalsFile .ssh/authorized_principals TrustedUserCAKeys /etc/ssh/trusted-user-ca-keys.pem
.ssh/authorized_principals basically need to output the same as the authorized_keys file eg
.ssh/authorized_principals
command="/app/gitea/gitea serv key-1 --config='/data/gitea/conf/app.ini'",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty principal
The difference is the principal instead of the ssh key, this should match the valid principals in your ssh certificate.
principal
In our case this will match with the usernames in gitea.
In the GUI there should be an option for a user to:
In the configfile, there should be an option to specify the system-wide CA (the contents of /etc/ssh/trusted-user-ca-keys.pem)
/etc/ssh/trusted-user-ca-keys.pem
It's possible to fit this in the public_key table by putting the correct principal in the content field instead of the ssh-key
public_key
content
I'm prepared to work on this.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Description
Support ssh certificates
This way users can get access without uploading a public ssh key, instead they are verified against a ssh CA.
This will need extra sshd configuration like this
.ssh/authorized_principals
basically need to output the same as the authorized_keys file egThe difference is the
principal
instead of the ssh key, this should match the valid principals in your ssh certificate.In our case this will match with the usernames in gitea.
In the GUI there should be an option for a user to:
In the configfile, there should be an option to specify the system-wide CA (the contents of
/etc/ssh/trusted-user-ca-keys.pem
)It's possible to fit this in the
public_key
table by putting the correct principal in thecontent
field instead of the ssh-keyI'm prepared to work on this.
The text was updated successfully, but these errors were encountered: