Can't login after switch to named user license

[peterrollier]

Hi,

The folowing code doesn't work anymore after we switched to a named user license in stead of a network license.

Can someone point me in the right direction?

loginResult = Vault.Library.ConnectionManager.LogIn(vlt_Server, vlt_Vault, Nothing, Nothing, Vault.Currency.Connections.AuthenticationFlags.WindowsAuthentication + Vault.Currency.Connections.AuthenticationFlags.ReadOnly, Nothing)

Thanks. 

[Anonymous]

If I had to guess I'd say it's the WindowsAuthentication part.  That is going to grab your current logged in user credentials, and unless you have single sign on with named user and its mapped to your current windows credentials, it's going to fail right there.  You probably need to change it to a Vault login account.

[peterrollier · Accepted solution]

Problem is solved, had to change the config file 

<Licensing edition="None"/>

[pvillella-CAP]

I'm running into this issue, as well. When Vault is set to Network license, the app gets a license just fine. Once we convert to Named User license, the app fails to get a license with this error 'Failed to acquire a license. Please try again later or restart the product.'

I tried making the change suggested by @peterrollier  -- changing <Licensing edition="None"/>.

However, now I get the error message "The license obtained is incompatible with the server", even if we set licensing back to Network.

We are using Vault Professional, so this value was previously set to <Licensing edition="Professional"/>

When set to 'Professional', we no longer get this error.

Vault client and the Vault job processor both start and pull a license on this machine just fine. We are logged in using the Autodesk user account and the user has Vault assigned.

Why can the Vault client get a license just fine but our app can't. Again, if set to Network licensing, it pulls a license just fine.

Thank you,

Patrick

[Anonymous]

Do you have access to the source code? Can you send the line of code over that shows how it's currently performing the login?

[pvillella-CAP]

Hi @Anonymous , I do have the source code.

That would be great if you would take a look at it. How should I get it to you?

Thank you,

Patrick

[tcp_wegener]

Hi Patrick,
as I understand <Licensing edition="None"/> does not work for you. Did you get a solution?

Could you share the line of code?

Thank you

Thomas

[tcp_wegener]

for me it works in 2022 in this way:

var adskAcount = AutodeskAccount.Login(IntPtr.Zero);
results = VDF.Vault.Library.ConnectionManager.LogIn(					 
  serverName: loginData.Server, // "localhost",
  vaultName: loginData.Vault, // "Vault",
  autodeskAccount: adskAcount, 
  authFlags: VDFCC.AuthenticationFlags.AutodeskAuthentication,
  progressCallback: null);

[cdellea]

Hi Thomas,

I am trying to implement Autodesk Id connection for my third-party application. I tried to manage the login as described in your message but it fails...

Autodesk Account login "fails" when calling :

var adskAcount = AutodeskAccount.Login(IntPtr.Zero);

 It just returns a "null" object.

And then, when calling :

results = VDF.Vault.Library.ConnectionManager.LogIn(					 
  serverName: loginData.Server, // "localhost",
  vaultName: loginData.Vault, // "Vault",
  autodeskAccount: adskAcount, 
  authFlags: VDFCC.AuthenticationFlags.AutodeskAuthentication,
  progressCallback: null);

 It fails returning the error "InvalidAutodeskAccount", "Autodesk credentials must be provided for sign-in."

I've tried with and without an active Autodesk Account connection on the machine I am running my application, the result is always the same.

Do you have any idea of whats going wrong ? Or should I do anything more ?

Thank you very much in advance for your help.

Colin

[larry.daubenspeck]

Peter, where is this config file of which you speak?