Feature Request
Teleport auth generates a certificate for the user with O= objects in it. It will be nice to have a mechanism to add more SAN fields by copying the O= objects to DNSNames and then passing it to GenerateCertificate function so that the certificate has roles encodes as SAN fields in it. like the following example,
X509v3 Subject Alternative Name:
email:all@goteleport.com, email:eng-staff@goteleport.com, email:eng-service-infra-team@goteleport.com
Usecase
There are certain apps that can be authenticated through the certificates. So it would be nice to have the SAN fields on the cert to make the authentication happen and carry the traits from the teleport.
Workaround
Access to these apps can be worked around using Teleport teleport JWT or SAML-based authentication but it would be nice to take advantage of cert-based authentication since the user is already logged into teleport and has a cert that can be used for accessing apps as well.
Feature Request Teleport auth generates a certificate for the user with
O=
objects in it. It will be nice to have a mechanism to add more SAN fields by copying theO=
objects toDNSNames
and then passing it toGenerateCertificate
function so that the certificate has roles encodes as SAN fields in it. like the following example,Usecase There are certain apps that can be authenticated through the certificates. So it would be nice to have the SAN fields on the cert to make the authentication happen and carry the traits from the teleport.
here is an example for cert based auth
Workaround Access to these apps can be worked around using Teleport teleport JWT or SAML-based authentication but it would be nice to take advantage of cert-based authentication since the user is already logged into teleport and has a cert that can be used for accessing apps as well.