"POST /sso/complete/saml HTTP/1.1" 301 5 "https://company.okta.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "10.96.64.109" 2024-07-25 14:40:18,557 ERROR [f924a3e35ad645a5857549526349008b] social 'Relay…

on the Okta side “Audience Restriction” was not set to the AWX base URL. After that "attr_email": "urn:oid:0.9.2342.19200300.100.1.3", "attr_username": "urn:oid:0.9.2342.19200300.100.1.1", "attr_last_name": "urn:oid:2.5.4.4", "attr_first_name": "urn:oid:2.5.4.42", "attr_user_perm…

Thats the post i mentioned. If you read the post it explains that the issue was ‘on okta side’ before that was the trailing slash. The post doesnt really provide helpful information to anyone having the same problem.

Bump. No one has experience getting SAML working? documentation is lacking important specifics and the only other post about the same error gives no solution

I have not set up SAML with AWX before (Okta or otherwise), so I cannot help you. @jdp11d might be able to help and answer questions since he did this recently. It’s not clear to me if it was the presence or the absence of the trailing slash “/” that caused an issue; however, aside from the “/” is…

I’ve read the guide as I mentioned. I don’t know why you’re replying if you can’t provide anything useful to the issue.

It isn’t clear what you have or haven’t done. You haven’t provided any snippets of your configurations on either the AWX or Okta side. The very post you claim has no solution claims that guide was all they needed besides fixing the trailing slash. You’re going to have to do the legwork to show us …

I have details above, the trailing slash issue isnt specified as to where and in the post there is mention of first it was trailing slash and then it was relaystate Ive posted the exact error from the logs and explained that the guide does not give details on what exactly is meant to be entered on …

Have you added the X_FORWARDED options to AWX? USE_X_FORWARDED_PORT = True USE_X_FORWARDED_HOST = True

Yes, those are relevant for csrf issues and I have those settings. The issue is relaystate.

If I had to guess, the Single sign on URL: in Okta needs to have the trailing slash, while the entity_id and url options on AWX may or may not need to have the trailing slash.

AWX SAML authentication with Okta - RelayState

Get Help

tvo318 (TVo) July 25, 2024, 5:21pm 2

Hi @trippinnik - have you looked at this discussion? Okta saml auth error social 'RelayState'. It appears to be a trailing “/” was what was breaking this.

Topic		Replies	Views
Okta saml auth error social 'RelayState' Get Help awx	5	431	June 8, 2024
Okta SAML setup with AWX 9.0.1 AWX Project awx	2	29	February 11, 2020
SAML Issues - RelayState Error AWX Project awx , aws	1	21	September 13, 2019
SAML integration error AWX Project awx	2	30	June 8, 2018
AWX / SAML / OKTA ? AWX Project awx	2	30	November 19, 2019

AWX SAML authentication with Okta - RelayState

Related topics