- Más nuevo
- Más votos
- Más comentarios
Finally I got an answer from AWS people:
If the Client VPN endpoint is configured using SAML-based authentication (such as Okta), then you > > have to use the AWS-provided client to connect:
https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/client-authentication.html#saml-requirements
And the promise to update the client documentation with a WARNING about this.
I hope for a Linux client..
The general theme of getting Linux client stuff from AWS is getting better, they provided the NOSQL workbench in Linux form recently.
Definitely, not sure why there is not, okta is kind of linux friendly openvpn no need to explain, so why there is not one, is probably the question.
Just to mention, previously as I stated, we used aviatrix, which provided a token that we can use as a password wehen askled and use standard OVPN configuration without any trouble, why not a simple similar solution.
Thanks Steven for triggering this response :-)
Edited by: tjc on Jun 26, 2020 6:32 AM
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años