Also the reason I think this is failing is because for some reason with
Tomcat it is not get the user name from IIS.  I do have integrated
windows authentication on.
 

Kevin Begosh, RSP

Tech Ops

Enterprise Business Services

301-791-3540 Phone

410-422-3623 Cell

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Jiri Pospisil
Sent: Tuesday, November 18, 2008 4:20 AM
To: [email protected]
Subject: Re: Single Sign On (SSO) Issue


** 

++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please Read The Disclaimer At The Bottom Of This Email

++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

Kevin,

 

I would look at the code in your custom authenticator jar file located
on the mid tier and see how it works out the user name. 

It seems that after the migration it cannot get the user name. 

 

Hope this gets you some idea.

 

Jiri Pospisil

 

IT Services 
LCH.Clearnet



 

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Begosh, Kevin
Sent: 17 November 2008 23:11
To: [email protected]
Subject: Single Sign On (SSO) Issue

 

** 

I am having an issue with Single Sign On.  I have a current environment
for the mid tier, IIS, Servlet Exec where SSO works.  We are looking to
change from Servlet to Tomcat on our mid tier servers.  In doing so it
looks like SSO is not working anymore.  SSO is not "Supported" by BMC
from what I have been told so my options are limited.  I was told by BMC
that there should be no issue changing what we have with SSO from
Servlet exec to tomcat.  We are on mid tier 7.1 patch 4, windows 2003,
IIS.  All the configurations on the AR Server is fine because it was
working before.  When I load the mid tier the log in screen pops up and
no visible errors appear.  From logging I am getting the following
issues

 

- Trying to load configuration arsys_api.xml
- Could not load optional configuration arsys_api.xml
- Trying to load configuration default.xml
- constructor(arcatalog)
- Trying to load configuration arsys_api.xml
- Could not load optional configuration arsys_api.xml
- Trying to load configuration default.xml
- Connects to ARServer *servername* through
[EMAIL PROTECTED]
- Api source is identified as: AP675689916919Q6UhSQhwYAAAKQAA
SSO: Initialization: Version 2.05e
SSO: Property values were loaded. 
usermethod:remoteuser
usercase:lower
removedomain:T
headername:
attname:
authmethod:default
authcustom:
debuglogging:T
- Unable to find required classes (javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.
SSO ERROR: RemoteUser name is null or empty. Using default login page
- Connects to ARServer *servername* through
[EMAIL PROTECTED]
SSO ERROR: RemoteUser name is null or empty. Using default login page
SSO ERROR: RemoteUser name is null or empty. Using default login page

 

it also makes reference to the custom authenticator failed, and that it
is using the default one.

 

And for the sake of the email I removed my server name under
*servername*, so that part was just my servers name.

 

Kevin Begosh, RSP

Tech Ops

Enterprise Business Services

301-791-3540 Phone

410-422-3623 Cell

[EMAIL PROTECTED]

 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

************************************************************************
*************************

 

This email is intended for the named recipient(s) only. Its contents are
confidential and may only be retained by the named recipient(s) and may
only be copied or disclosed with the consent of LCH.Clearnet Limited. If
you are not an intended recipient please delete this e-mail and notify
[EMAIL PROTECTED]

 

The contents of this email are subject to contract in all cases, and
LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy. LCH.Clearnet Limited accepts no liability,
including liability for negligence, in respect of any statement in this
email.

 

LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High
Street, London EC3N 1EA. Recognised as a Clearing House under the
Financial Services & Markets Act 2000. Reg in England No.25932 

Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com

 

************************************************************************
*************************

 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to