Http authentication using BasicSecurityFilter

Helen <[email protected]> Fri, 17 Aug 2007 15:14:47 -0700
Newsgroups gmane.comp.java.xplanner.devel
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============0479229514==
Content-Type: multipart/alternative;
	boundary="------------020207040505060404070300"

This is a multi-part message in MIME format.
--------------020207040505060404070300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi.  I am trying to connect to XPlanner (.7b7) using the SOAP API, and 
everything works fine until I try to use Http Authentication.  It 
actually works if the http username/password are the same as the 
XPlanner user name/password, but if these are different, the user is not 
found.  I traced it to the BasicSecurityFilter implementation, which 
uses the http credentials to search for and XPlanner Person -- if these 
are different, it obviously doesn't work, since the Person is not 
found.  Is it the design to have the http authentication credentials be 
the same as the XPlanner credentials? 
 
BTW, When connecting through a browser, the FormSecurityFilter takes 
effect on the server side, which does allow the http authentication 
credentials to be different from the XPlanner credentials.
 
Could anyone help me figure out if I am not setting something up 
correctly, or if this is the design of the http authentication 
implementation for SOAP in XPlanner?
 
Thanks a lot
-Helen

--------------020207040505060404070300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<div><font face="Arial" size="2"><span class="665382322-14082007">Hi.&nbsp;
I am trying to connect to XPlanner (.7b7) using the SOAP API, and
everything works fine until I try to use Http Authentication.&nbsp; It
actually works if the http username/password are the same as the
XPlanner user name/password, but if these are different, the user is
not found.&nbsp; I traced it to the BasicSecurityFilter implementation,
which uses the http credentials to search for and XPlanner Person -- if
these are different, it obviously doesn't work, since the Person is not
found.&nbsp; Is it the design to have the http authentication credentials be
the same as the XPlanner credentials?&nbsp;</span></font></div>
<div><font face="Arial" size="2"><span class="665382322-14082007"></span></font>&nbsp;</div>
<div><font face="Arial" size="2"><span class="665382322-14082007">BTW,
When connecting through a browser, the FormSecurityFilter takes effect
on the server side, which does allow the http authentication
credentials to be different from the XPlanner credentials.</span></font></div>
<div><font face="Arial" size="2"><span class="665382322-14082007"></span></font>&nbsp;</div>
<div><font face="Arial" size="2"><span class="665382322-14082007">Could
anyone help me figure out if I am not setting something up correctly,
or if this is the design of the http authentication implementation for
SOAP&nbsp;in XPlanner?</span></font></div>
<div><font face="Arial" size="2"><span class="665382322-14082007"></span></font>&nbsp;</div>
<div><font face="Arial" size="2"><span class="665382322-14082007">Thanks
a lot</span></font></div>
<div><font face="Arial" size="2"><span class="665382322-14082007">-Helen</span></font></div>
</body>
</html>

--------------020207040505060404070300--


--===============0479229514==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
--===============0479229514==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xplanner-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xplanner-devel

--===============0479229514==--