Forum Discussion
Exchange Outlook Anywhere Authentication Issue
Dear All,
I am facing an issue in authentication when i am trying to configure Outlook, its getting configured from Control Panel > Mail, and then its asking to restart my Outlook. After Doing so the Mailbox is been retrieved, But the issue start during the process, I keep getting the Username and password prompt. Even though entering for several times its not connecting. I get the below logs in the APM logs. Please help me to solve the Issue.
Thanks in Advance.
2014-11-26 16:21:52 Session variable 'session.logon.last.result' set to '1' 2014-11-26 16:21:52 Session variable 'session.logon./Common/test_exchange_act_logon_page_ag.username' set to 'mmubeen' 2014-11-26 16:21:52 Session variable 'session.logon./Common/test_exchange_act_logon_page_ag.logonname' set to 'mmubeen' 2014-11-26 16:21:52 Session variable 'session.assigned.uuid' set to 'tmm.uuid.a868650ec63aac446a89796d5144811b' 2014-11-26 16:21:52 Session variable 'session.ad.last.errmsg' set to ' ' 2014-11-26 16:21:52 Session variable 'session.ad.last.actualdomain' set to 'ME.ALINMA.INTERNAL' 2014-11-26 16:21:52 Session variable 'session.ad./Common/test_exchange_act_active_directory_auth_1_ag.' set to '1' 2014-11-26 16:21:52 Executed agent '/Common/test_exchange_end_allow_ag', return value 0 2014-11-26 16:21:52 Following rule 'fallback' from item 'SSO Anywhere' to ending 'Allow' 2014-11-26 16:21:52 Following rule 'fallback' from item 'Variable Assign Anywhere' to item 'SSO Anywhere' 2014-11-26 16:21:52 Username 'me\mmubeen' 2014-11-26 16:21:52 Executed agent '/Common/test_exchange_act_active_directory_auth_1_ag', return value 0 2014-11-26 16:21:52 Websso basic authentication for user 'me\mmubeen' using config '/Common/HTTP_Basic_OWA' 2014-11-26 16:21:52 AD agent: Auth (logon attempt:0): authenticate with 'mmubeen' successful 2014-11-26 16:21:52 \N: Username used for SSO contains domain information. Please enable 'Split domain from full Username' option in Logon Page if domain info should be separated from username for SSO to work properly 2014-11-26 16:21:52 AD module: authenticate with 'mmubeen@ME.ALINMA.INTERNAL' successfully 2014-11-26 16:21:52 Session variable 'session.sso.token.last.username' set to 'me\mmubeen' 2014-11-26 16:21:52 Session variable 'session.policy.result' set to 'allow' 2014-11-26 16:21:52 Session variable 'session.logon.last.username' set to 'me\mmubeen' 2014-11-26 16:21:52 Session variable 'session.logon.last.logonname' set to 'mmubeen' 2014-11-26 16:21:52 Session variable 'session.logon./Common/test_exchange_act_logon_page_ag.result' set to '1' 2014-11-26 16:22:44 basic authentication auto add credential, session id : \N 2014-11-26 16:22:44 metadata len 317 2014-11-26 16:22:44 Websso basic authentication for user 'me\mmubeen' using config '/Common/HTTP_Basic_OWA' 2014-11-26 16:22:44 \N: Username used for SSO contains domain information. Please enable 'Split domain from full Username' option in Logon Page if domain info should be separated from username for SSO to work properly 2014-11-26 16:22:45 basic authentication auto add credential, session id : \N 2014-11-26 16:22:45 metadata len 317 2014-11-26 16:22:45 Websso basic authentication for user 'me\mmubeen' using config '/Common/HTTP_Basic_OWA' 2014-11-26 16:22:45 \N: Username used for SSO contains domain information. Please enable 'Split domain from full Username' option in Logon Page if domain info should be separated from username for SSO to work properly 2014-11-26 16:23:09 basic authentication auto add credential, session id : \N 2014-11-26 16:23:09 metadata len 317 2014-11-26 16:23:09 Websso basic authentication for user 'me\mmubeen' using config '/Common/HTTP_Basic_OWA' 2014-11-26 16:23:09 \N: Username used for SSO contains domain information. Please enable 'Split domain from full Username' option in Logon Page if domain info should be separated from username for SSO to work properly 2014-11-26 16:23:10 basic authentication auto add credential, session id : \N 2014-11-26 16:23:10 metadata len 317
1 Reply
- Michael_Jenkins
Cirrostratus
Have you been able to resolve this problem? If not, there may be a couple things you could try.
If you were to connect directly to the Exchange server, what username would you need to use? You could try using tcpdump to capture the traffic between client and F5 and F5 and backend server. I assume you'll be using HTTPS, so you would need to use ssldump to decrypt the packets as well. You may be able to see better the request/response with the backend server and determine where the issue is happening.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com