Re: Http authentication using BasicSecurityFilter
Helen <[email protected]> Fri, 24 Aug 2007 15:23:52 -0700
| Newsgroups | gmane.comp.java.xplanner.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============1110221834== Content-Type: multipart/alternative; boundary="------------030102060906040908090507" This is a multi-part message in MIME format. --------------030102060906040908090507 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Jacques. Thanks for your reply. I was talking about credentials configured for a server set up to do http authentication. So these would be username/password necessary to just get to the server itself before being able to even communicate with XPlanner. I am not sure how else to do it, other than configuring additional settings for xplanner username/password somehow. It just looked confusing to me to be able to do this from a browser with different sets of credentials, and using the SOAP API only having them be the same. Thanks -Helen Jacques Morel wrote: >I haven't had the time to research this deeply so I am answering with >the best of my memory. >I am not sure what you are refering with http credentials. If they are >the userid and password used to connection through SOAP, they have to >match a user id in xplanner database. How do you suggest the mapping >be done if it wasn't like that? >Something tells me I did not understand your question ;-) > >Jacques > >On 8/17/07, Helen <[email protected]> wrote: > > >>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 >>------------------------------------------------------------------------- >>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/ >>_______________________________________________ >>Xplanner-devel mailing list >>[email protected] >>https://lists.sourceforge.net/lists/listinfo/xplanner-devel >> >> >> >> > >------------------------------------------------------------------------- >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/ >_______________________________________________ >Xplanner-devel mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/xplanner-devel > > > --------------030102060906040908090507 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"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Jacques. Thanks for your reply.<br> <br> I was talking about credentials configured for a server set up to do http authentication. So these would be username/password necessary to just get to the server itself before being able to even communicate with XPlanner. I am not sure how else to do it, other than configuring additional settings for xplanner username/password somehow. It just looked confusing to me to be able to do this from a browser with different sets of credentials, and using the SOAP API only having them be the same.<br> <br> Thanks<br> -Helen<br> <br> Jacques Morel wrote: <blockquote cite="mid2ae5715c0708240121w6d4e2ad9xdaabcb213fdf06d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org" type="cite"> <pre wrap="">I haven't had the time to research this deeply so I am answering with the best of my memory. I am not sure what you are refering with http credentials. If they are the userid and password used to connection through SOAP, they have to match a user id in xplanner database. How do you suggest the mapping be done if it wasn't like that? Something tells me I did not understand your question ;-) Jacques On 8/17/07, Helen <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> 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 ------------------------------------------------------------------------- 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 >> <a class="moz-txt-link-freetext" href="http://get.splunk.com/">http://get.splunk.com/</a> _______________________________________________ Xplanner-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/xplanner-devel">https://lists.sourceforge.net/lists/listinfo/xplanner-devel</a> </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------------------------- 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 >> <a class="moz-txt-link-freetext" href="http://get.splunk.com/">http://get.splunk.com/</a> _______________________________________________ Xplanner-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/xplanner-devel">https://lists.sourceforge.net/lists/listinfo/xplanner-devel</a> </pre> </blockquote> <br> </body> </html> --------------030102060906040908090507-- --===============1110221834== 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/ --===============1110221834== 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 --===============1110221834==--