topic Re: Reconnect for third party clients in Vault Customization Forum

Reconnect for third party clients

FedotovAnton — Mon, 08 Feb 2016 07:10:25 GMT

Hello,

how to perform reconnect for current logged in user (ticket)? I tried to use "SignIn" method with ticket and user uid - but it takes a second license. Or I need to perform "SignOut" then again "SignIn"?

Anton.

Re: Reconnect for third party clients

Patrick.Gruber — Tue, 09 Feb 2016 07:02:36 GMT

Hi FedotovAnton,

I have just looked up in the Vault SDK documentation and found this:

public void SignIn( 
   System.string dataServer,
   System.string userName,
   System.string userPassword,
   System.string knowledgeVault
)

If the Vault server is using network licensing, the sign in will consume license.

public void SignOut()

Clients should sign out before exiting. If the Vault server is using network licensing, the sign out will free up the license.

So, to answer your question: First, you have to make a sign out before you re-signIn with the user.

Re: Reconnect for third party clients

minkd — Wed, 10 Feb 2016 19:43:00 GMT

Anton,

Can you describe what you mean by "reconnect"?

Are you referring to the "automatic re-signin" support in SDK?

-Dave

Re: Reconnect for third party clients

FedotovAnton — Fri, 12 Feb 2016 07:42:02 GMT

Hello, thanks for the replies, guys!

By reconnect i mean: I connect to the Vault 2016 and consume a license - if I do not perform anything inside my app (for example 5 minutes), then I get error and I need to reconnect. When I do It - I consume another license. The question is - is there a method to reSignIn whit existing ticket/uid, or SignOut - then SignIn?

May be you know what the "SignInAltLicense" method does?

Thanks.

Re: Reconnect for third party clients

minkd — Fri, 12 Feb 2016 16:52:41 GMT

Are you using the SDK? The SDK provides an automatic re-signin capability via the WebServiceManager class. However, this automatic re-signin is not supported with all of the credential classes - for instance it is not supported if you use the UserIdTicketCredentials class. It works by attempting a re-signin (just once to avoid an infinite loop) when an error 300 (BadToken) exception is received.

Applications should have a corresponding SignOut for any SignIn. The WebServiceManager class does a SignOut when it is disposed.

A background job on the server (which runs every 5 minutes) will close sessions that have been inactive for over 30 minutes. Therefore, you shouldn't be losing your session unless you haven't made any web-service calls for 30 to 35 minutes unless IIS is recycling the worker process. If the worker process is recycled all licenses are released until clients do their automatic re-signin.

Licenses are shared based on the vault username and the client host. This is why running Inventor (with vault) and the Vault Explorer client at the same time results in only 1 license being obtained. They are not sharing a "connection" because they are running in different process spaces. This sharing occurs on the server so clients do not need to do anything special for it to work. What indication are you seeing that makes you believe you are consuming two licenses?

SignAltLicense is for internal Autodesk use only - there is no way for a third party application to make use of it.

-Dave