Thread Info
  • State Not Answered
  • Replies 2 replies
  • Subscribers 4 subscribers
  • Views 8884 views
  • Users 0 members are here
Options
Suggested

WAF Bug in 9.570-20 - RPC over HTTPS and Outlook 2019 ask for password at start.

Alex76

Hi,

after i start the beta i update my outlook from version 2016 to 2019 and i have a interessting bug:

 

- If i'am internal, outlook 2019 use rpc - the normal way.

- If I'am external, i have configured the WAF for use a RPC over HTTPS Profile and the password will not work, but outlook is allready connected. I don't know what outlook here like todo. 

- If I'am external and i configure ,,none" as WAF Firewall profile, i don't have this issue, outlook is connected hole the time and don't ask for a password. 

So i think there is a issue with the RPC over HTTPs, but i can not exacly say, if this problem exists with the normal version too or only with the Beta. 

 

kind regards

 

Alex

Parents Reply Children
  • 0 in reply to Holger Gran

    I think, i have a similar Problem - Outlook 2019 wants to open mail.domain.xy/api and gets a 401 error.

    When i open the URL internally (behind the WAF) - i can Authenticate. Externally i can't authenticate (with the same Credentials).

     

    2018:11:11-20:33:28 xxxxx-1 httpd: id="0299" srcip="xxxxx" localip="xxxxx" size="0" user="-" host="xxxxx" method="GET" statuscode="401" reason="-" extra="-" exceptions="-" time="12415" url="/api" server=".remotewebaccess.com" port="443" query="" referer="-" cookie="X-BackEndCookie=S-1-5-21-1200671020-1714986119-704727385-1117=u56Lnp2ejJqByc/JnprJysbSyJqcmtLLmcbM0sabxxxxxxxxxxxxx/GxcrPgbG6rKyzuq3Rk5CcnpOBzw==; exchangecookie=1bc462d14fb84aca8f6a7efa8681b341" set-cookie="-" websocket_scheme="-" websocket_protocol="-" websocket_key="-" websocket_version="-" uid="xxxxxxx"
Unfiltered HTML