Hello Preston,

I saw there is a method verifyPasswordRequest, which I figured out is to just verify the password. (What a surprise.)
So I tested it with some handmade xml and, it seemed to work.
I however noticed a test failing after changing my app to use this call for handling the login.
I ignored it since I was in a hurry, and then a tester noticed he could login using an incorrect password. Yikes!

After some debugging I figured it out, the returned xml is a little off:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
  <s:Header />
  <s:Body>
    <verifyPasswordResponse>
      <status>
        <code>53273</code>
      </status>
    </verifyPasswordResponse>
  </s:Body>
</s:Envelope>
I think according to the schema, it should be more like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.novell.com/2005/01/GroupWise/methods" xmlns:gwt="http://schemas.novell.com/2005/01/GroupWise/types">
  <s:Header />
  <s:Body>
    <verifyPasswordResponse>
      <status>
	    <gwt:code>53273</gwt:code>
      </status>
    </verifyPasswordResponse>
  </s:Body>
</s:Envelope>
Since it is an integer, the xml parser was setting the status code default value to 0 when the value is not found.
0 is the success code, so it ended up being success by default! Not too good in this case.
Needless to say I changed the constructor of my Status object to defaulting the status code value to -1.
How are you going to handle this? Will you change the wsdl or the generated response?
Anyone currently using this method could possibly run into the same problem as me, being able to login with any password.