<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi All,<o:p></o:p> <o:p> </o:p> This is a rather strange one. Is there any support for determining SASL mechanisms based on the user’s name? I [will] have a bunch of authentication providers, such as EXTERNAL, SQL, SAP, NTLM, Kerberos, Open-Id etc. These can be located on the component itself or on another component on the network: it doesn’t matter (ooh, you should see my framework :)). The thing that I worry about is that obviously some components won’t support other authentication mechanisms (NTLM is a good example of this): so if I just query them verbatim for mechanisms there is no guarantee that the client will be able to use that mechanism to log in (e.g. Joe might be on the domain, but not in the SQL DB, failure if he tries to use DIGEST-MD5 – his client may even always fail to log in).<o:p></o:p> <o:p> </o:p> I thought that I could use the “to” attribute on the <stream:stream> tag, but another problem arises: most of the blumming client’s I have analyzed using my server don’t put this in the start tag: I am sure there is a reason I missed on the mailing list (is there?).<o:p></o:p> <o:p> </o:p> I basically want to say to the components, “does anyone know this guy? How do I talk to him?” and if they respond I can aggregate the results, if not I can use a predefined list of mechanisms (to fool harvesters/hackers).<o:p></o:p> <o:p> </o:p> Maybe I could leave it up to the users to complain to the misbehaving client developers?<o:p></o:p> <o:p> </o:p> Thanks guys.<o:p></o:p> </div> </body> </html>