Invalid User Name and/or Password

Hey Annie_Murphy 

Ok - so considering you said you had no auth issues prior to the upgrade, but once upgraded you started getting invalid logon creds warning and even switching to different versions of ReadyAPI - the auth problems still remain.

If no changes were made to the auth details on your tests immediately prior to the upgrade, then it's reasonable to infer that something has become corrupted in the cred details for the underlying project.xml file (or composite file).

As changing the versions of ReadyAPI hasn't reverted your invalid creds change (and it shouldn't have), we can again infer that this has nothing to do with the ReadyAPI version you're running and again, the issue is with the underlying project file(s).

Can you confirm if your project is saved locally - or are you using a shared project file?

Can you confirm if your project is saved as a single .xml file or the project saved as a composite (multiple discrete files that make up the project file)?

Depending on your answers will guide us how to proceed.

If it's a shared file - and other people using their ReadyAPI instances have no auth problems, but when you open the same shared project file(s) on your ReadyAPI instance and you get auth issues, then this is really weird and I can't see how that could happen.

As I say above - if you can answer the questions - this will guide us on how to proceed.

Just as an aside - have you compared the RAW SOAP request content (especially the auth details) of what you are submitting in ReadyAPI compared with the RAW SOAP request content (especially the auth details) that your colleagues are submitting?  We could then see the differences between what you are submitting in ReadyAPI relative to your colleagues which would then indicate how to fix.

Cheers,

Rich