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:
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
Error while connecting to SQL Server Express Edition from SCTasked a year ago
Connecting Users to AWS Athena and AWS Lake Formation via Tableau Desktop using the Simba Athena JDBC Driver and Okta as Identity Providerasked 5 months ago
Issues connecting to Postgres RDS instance from within a VPCasked 3 years ago
ERR_SIG_TIMEOUT: An error occurred while connecting to your WorkSpace.asked 6 years ago
Connectivity issues across all ec2 related resourcesasked 3 years ago
Connecting a Linux box to AWS-VPN using OKTA Authentication/Authorizationasked 2 years ago
CloudWatch error : An error occurred while describing log groups : Rate exceededasked 4 months ago
i am using free tier as a new user. i am connecting my EC-2 instance from my laptop through putty.Accepted Answerasked 3 months ago
Problem to enter my linux instanceasked 2 years ago
After making an image and creating a bundle I get a repeated errorasked a year ago