1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
AWS Client VPN with SAML based federated access ONLY supports the official AWS Client VPN Software.
You can not use 3rd party VPN Software (open vpn client) if you are using federated access. To use 3rd Party VPN Software, you have to use certificate based authentication.
It is also confirmed here https://docs.aws.amazon.com/vpn/latest/clientvpn-user/linux.html
Conteúdo relevante
- AWS OFICIALAtualizada há 9 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 9 meses
I guess I can still use a variation of AWS AD, potentially AWS AD Connector. In our case certificate based authentication is not an option. But I've got the point about the "federated access" part. Thanks
Yeah you may have to create an AWS managed AD and then create a trust with your azure ad and use AD auth. 100% I agree, I wouldn’t use certificates. I have in the past but it’s far easier with SAML with azure that I’ve setup in the past. Good luck hope you get to a working solution.