SQL Server Global Access Tokens

Answered

Comments

2 comments

  • Avatar
    Yaniv Levi

    Hi Sylvia,

    When creating an access token, the option provided by the access token to configure it is mandated by the third party to connect with, in your case this would be SQL Sever.

    So, the options to configure the Access Token for SQL Server are based on the supported "connection string" format for SQL Server.

    When passing user name and password as part of the connection string, this would be SQL user and not a domain user, so, when you uncheck the "SSPI (Integrated Security)" and provide values in the "User Name" and "Password" fields - this must be SQL user credentials.

    Unfortunately, there is no way (unless implementing impersonation mechanisms) to pass domain user as part of a connection sting to SQL Server other than using the SSPI option (Integrated Security), which will use the AgilePoint Service Instance Account. 

    NOTE - SSPI option only works if the domain account is the one opening the connection. This will be true whenever AgilePoint Server instance account is a domain user (applicable in most env where AgilePoint integrates with Active Directory).

    BTW - Have a look at connectionstrings.com for every possible variation - a great resource for all connection string usages and options.

    Hope this clear out and help.

    Thanks,

    Yaniv.

    0
    Comment actions Permalink
  • Avatar
    Sylvia Able

    Thanks for your response, Yaniv!

    0
    Comment actions Permalink

Please sign in to leave a comment.