Mariusz,
I think I jumped too quickly to solving the Integrated Windows Authentication problem. On your second pass, I realize I should have paid closer attention to the specific exception you reported. The VersionOne meta-data layer does not require authentication. Therefore, authentication does not prevent the SDK from finding known AssetTypes. Connection problems can cause that.
One common cause is a malformed URL passed to the SDK. The most common problem is a missing trailing slash. But, if you had an application working prior, this is an unlikely cause for you.
You mentioned that you did have a proxy before the upgrade. This is the next most common cause and seems to be the most likely cause in your case. I'm not sure I entirely understand the network model from your description. When you say VersionOne is "hosted" (in response to my question), do you mean VersionOne is on-premise (your premises), or hosted with us? Do you use Windows Authentication with the proxy? When VersionOne authentication was changed, did the proxy also change authentication?
Ian
On Friday, June 29, 2012 7:01:06 AM UTC-4, Mariusz Francuz wrote:
Hello Ian,
I tried your hint but it didn't help. I still get the same exception. As it comes to the proxy, before I was passing the information using java options, I tried the other constructor with proxySettings just to check if this could help. There is one difference that I can observe. If I use the constructor with proxySettings then on e.g. getProjects() I get exception:
com.versionone.apiclient.MetaException: Unknown AssetType: Scope
If I use the simpler constructor and use java options for proxy then I get:
[Fatal Error] :80:3: The element type "table" must be terminated by the matching end-tag "</table>".
com.versionone.om.SDKException: Cannot execute query.
It seems that it doesn't matter what do I pass to V1Instance - even dummy user and password result in the same.
Do you have any other ideas, what may be wrong?
Regards,