# Using AWS "ALB" to front end for AWX, difficulties with SAML **URL:** \ **Category:** AWX Project\ **Tags:** aws, awx\ **Created:** [April 2, 2020, 7:24pm UTC](https://forum.ansible.com/t/using-aws-alb-to-front-end-for-awx-difficulties-with-saml/32590 "2020-04-02T19:24:59Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Kadel-Garcia\_Nico](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@Kadel-Garcia\_Nico](https://forum.ansible.com/u/Kadel-Garcia_Nico)\ **Post date:** [April 2, 2020, 7:24pm UTC](https://forum.ansible.com/t/using-aws-alb-to-front-end-for-awx-difficulties-with-saml/32590/1 "2020-04-02T19:24:59Z")
Let me reach out again about this. I’ve an AWX environment deployed in AWS for testing. For various reasons, I don’t care to host the relevant SSL keys locally and wish to use an ALB in front of it. This is all well and good, It works, and I can do direct logins with my preset “admin” credentials and configure things. I’ll call this host “[awx-dev-2.example.com](http://awx-dev-2.example.com)”. The ALB is passing traffic for [https://awx-dev.example.com](https://awx-dev.example.com). I also need to use SAML, specifically OKTA based SAML to authenticate to it. I’ve succeed in registering the host in SAML, it presents a SAML login icon, clicking it connects me to OKTA and they send an authentication request. When I acknowledge it, I see a screen flash mentioning “[awx-dev-2.example.com](http://awx-dev-2.example.com)” and get presented to the login page. And if I try clicking on the SAML icon again, it says I’m already authenticated, even though I can’t access anything. I’m trying to figure out which of these factors may be contributing. “X-Forwarded-For”, settings, maybe? Has anyone else gotten SAML and an ALB playing nicely together? Or do I need to use a Classic Load Balancer, which I could in fact do? **Nico Kadel-Garcia** Senior DevOps Engineer Cengage Learning 200 Pier Four Blvd. Boston, MA 02210 [nico.kadel-garcia@cengage.com](mailto:nico.kadel-garcia@cengage.com)