Here in the below code we found that the parameter passed in the function "VerifyAndDecryptToken" is "Password" while as per
the defintion of the function "VerifyAndDecryptToken" this function accepts serializedToken as parameter.


public bool Authenticate(string username,
string password,
string sourceIp,
[System.Xml.Serialization.XmlAnyElementAttribute()] System.Xml.XmlElement[] Any)
{
if (username.IndexOf("@") == -1)
return false;

AuthToken t = VerifyAndDecryptToken(password);
if ((t == null) || (t.Username != username))
return false;

return usedids.IsNewId(t.TokenNumber, t.Expires);
}


So when SFDC invokes the Authenticate function of the intranet webservice and when data like "password" is passed as argument to
the function "VerifyAndDecryptToken" instead of the actual token we get the following error in the function "VerifyAndDecryptToken"

Error: Server was unable to process request. ---> Invalid character in a Base-64 string.

So please let us know if there is issues withing this function where token should be passed to the function instead of the password?

Also is it possible to have determine the 'Token" data in this function so that it can be passed as an argument to the "VerifyAndDecryptToken" function?

As for testing when we used hardcoded Token value in the "VerifyAndDecryptToken" function we were able to login to the account for which SSo is enabled.

We were able to login only when we used a hardcoded token value as mentioned in the below modified function.

internal static AuthToken VerifyAndDecryptToken(string serializedToken)
{
serializedToken = "cAEAAH390j9AjEKZy+2U8Rd2CpaGxad9mYV2ZN1W83TWZYlphWvKgJaAa+4ju7wBJloBd3bZiQZ+1S9fnrwNBdSYJOopBA+TIDtckBbaDPwD/9nHUuvX3Pq7FEdULjReqY0I+T388d+STQQMXk4Douj/OXoQWv8mBZo73Da6xpsCLWwE3CuSxsXIhBD0lluY1NfjkQ2dL95L8G1eBM1ts3rW5pifJGjsPc2goce+NRzcA5ChBNntOXKAlNW7rFLGFOPPHETRpecflFyrY90GXFeh7dulXqyiKoRDvXe60IZDTaypnlEfiIue/x5MEMnJqK/fOviwUoUm/KBaxxyz4ah5oMXLaTOmT34FpZFChJkeOIXP2T2Wi8LxRtTsfgA+PKhTYUXwPypsjmyJdE5znPCH+OlazR/e2Lsgr1OksIwBgXldU8ua5q+akN4BWvS3Fzwnze6TiqS+XAzEQXDieFMgWsyPMkrhnaJ6EojWanSjqaVbANA0NnJF+A9yxDChpSGuUTqxiumKP0UK4GH3vIB8j5KtTs3l9cimTT10dGUla3JYBobAC6S1KpvWVA5xvTE88a/Fzzvcu8C3z2tREeE33tSWbG+zyUR148OutBob0GXpLeTTIaUz+i/I7v8YxOoHnuCMtaChOkbYIUqCK+Hu1P0=";
// unpack the string into the data & sig
byte[] data, sig;
if (!UnpackSerializedString(serializedToken, out data, out sig))
return null;
// verify the signature
if (!GetSigningRsa().VerifyData(data, new SHA1CryptoServiceProvider(), sig))
return null;
// decrypt the data
byte[] token = Decrypt(GetEncRsa(), data);
AuthToken t = DeserializeToken(token);

return t;
//if (!t.Expired)
// return t;
//return null;
}

Can anybody help us resolve this issue?

 

Also can anybody let us know whether the code provided by SFDC in  [Salesforce.com_Delegated_Authentication.zip] is a production ready solution or there is some additional coding required to be done in the code provided.