For SAML login, is private key necessary? #3204
-
The doc I found around authentication with solution user only mentions presenting cert instead of the key
But looking at the sessions/login.go and related test, looks like cert is required when creating solution user and when getting a saml token, both key and certificate are required. Is that true? So I can use any certificate and key to create user and login, but then for other vsphere connection, I assume I still need the tlsthumbprint or vsphere's CA? I think this cert will only used for retrieving token. Is that correct? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi @lubronzhan , The Lines 59 to 64 in b504836 We do the same in this sts test when creating a solution user: Line 58 in b504836 When using Other than govmomi/govc usage, have you looked at vSphere cloud provider? https://github.com/kubernetes/cloud-provider-vsphere/blob/65f264e5adc2daa8162348fd69b06b56c84480fd/pkg/common/vclib/connection.go#L147-L149 |
Beta Was this translation helpful? Give feedback.
Hi @lubronzhan ,
The
ssoadmin
endpoint where users, groups, etc., are managed has its own session manager and only supports SAML token authentication. But a bearer token (issued with username+password) can be used, that's the default for the govc sso related commands, which use this helper:govmomi/govc/sso/client.go
Lines 59 to 64 in b504836
We do the same in this sts test when creating a solution user:
govmomi/sts/client_test.go
Line 58 in b504836