02-25-2010
08:40 PM
- last edited on
03-25-2019
09:34 PM
by
ciscomoderator
Using Outlook plug-in with SSO enabled and when viewing the log files the current signed in user account is being passed back but the domain is blank. While the account does exist in MeetingPlace it doesn't even get to domain filter check. Anyone seen an isue like this? Account is logged into workstation with domain account and connected to Exchange Server with domain account.
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,721 [INFO ,AuthorizationFilter 115] SCHED_AS : null, SSO_DOMAIN : , REMOTE_USER : xx99
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,721 [INFO ,SystemConfigurationManagerImpl 6526] getOutlookAuthMethod START
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,724 [INFO ,SystemConfigurationManagerImpl 6530] getOutlookAuthMethod END :: auth. method=SSO
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,724 [INFO ,AuthorizationFilter 131] SSO_DOMAIN : , REMOTE_USER : xx99
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,725 [INFO ,AuthorizationFilter 365] domain name is null or empty, SSO validation fails [--outlook--][http-443-Processor122] 2010-02-23 15:35:18,725 [INFO ,SystemConfigurationManagerImpl 962] getSystemDefaultLocale START
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,727 [INFO ,SystemConfigurationManagerImpl 988] getSystemDefaultLocale END :: defaultLocale :1
[--outlook--][http-443-Processor122] 2010-02-23 15:35:18,729 [INFO ,AuthorizationFilter 336] session is null
03-08-2010 07:16 PM
Hi -
In the information you provided, I do see what appears to me as a red flag - http with 443. 443 is the https (secured port) whereas http should be port 80. Here is a link to troubleshooting for single-sign on authentication for MeetingPlace - http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_tech_note09186a00807ec20d.shtml#topic2
Regards, Ginger
03-08-2010 07:35 PM
With 7.0.2 you have to use SSL with single sign-on. TAC had me upgrade to 7.0.2.14 and then 7.0.2.53 hotfix. Now instead of passing the userid it passes a Exchange alias and the email domain. It's now back with development.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide