I hope someone will read this as this is not a new question, but relates to the same topic.
I also have an OWA2013 application and we have an APM based on 10.2.4 in front of it. Logon page and AD auth works fine, but then SSO is failing. I'm just getting forwarded to the OWA logon mask and the username from the APM logon page is already filled in. I sniffered the traffic on the serverside and there is only ONE HTTP-request towards the URI "/owa/auth/logon.aspx" (issued from the floating SNAT automap address), but in my SSO config I entered in the Form Action field "/owa/auth.owa" (catched that value from the source code of the OWA logon page). Should I see the SSO request also from the SNAT-address or will this be issued from the local self-IP?
Can anybody help me here, what's or where the issue is? Or how can I further troubleshot this? And is it normal that in the APM session log only the session.sso.token.last.username is mentioned? Because it seems that the password will not be correctly transferred to the OWA logon page.
Thank you!
Ciao Stefan :)