Checking inside method preAuthAccount,
uses the parameters in different order than is explained in Zimbra wiki.
concat the values for account, by, expires, timestamp together
(in that order, order is definitely important (Zimbra Wiki)
This is code for preAuthAccount method.
XMLElement req = new XMLElement(AccountConstants.AUTH_REQUEST);
Element a = req.addElement(AccountConstants.E_ACCOUNT);
a.addAttribute(AccountConstants.A_BY, "name");
a.setText(accountName);
Element p = req.addElement(AccountConstants.E_PREAUTH);
p.addAttribute(AccountConstants.A_TIMESTAMP, timestamp);
p.addAttribute(AccountConstants.A_BY, accountBy);
p.addAttribute(AccountConstants.A_EXPIRES, expires);
p.setText(preAuth);
invoke(req);
¿Could be this the problem?
Anybody has tried this method in SoapProvisioning class?
Thanks |