Post reply

How to logout from SSMS 2016 (Microsoft SQL Server)?

  • July 21, 2017 at 6:13 am

    #338367

    I've implemented the Always Encryption to encrypt the SSN field for a Patient table in my Azure DB.(Using Azure Key Vault as my Key Store Provider)

    I'm using SSMS 2016(13.0.16100.1) as Client Tool.
    Initially, I tried to execute the simple select statement for that particular Patient table. It comes with the pop-up to Sign-up (see below image).So, that I can sign-in with my account in order to decrypt my SSN column.

    Here I experienced 2 types of cases:

    CASE 1

    Not able to log out from the current Credentials

    Assume that for the first time itself I entered valid credentials( who can have access to decrypt the key @ssn)

    In this case, those credentials were saved somewhat internally. I couldn't able to log out from my credentials.

    Initially, i'm thinking that the credentials were saved on session based.So it will work only for that particular session.But it's not...

    The same credentials will work for different sessions, even I've tried with closing my SSMS and reopen in another window still using the old credentials.

    CASE 2

    Not able to Re-enter the credentials

    Assume that for the first time itself I signed with In-valid credentials( who doesn't have access to decrypt the key @ssn)

    In this case, i couldn't able to decrypt the SSN column .So again the credentials where saved somewhat internally.

    So if i want to re-enter with my valid credentials.I couldn't do it.

    I think in order to solve the both CASES there will be a single solution=>LOGOUT FROM THE CURRENT CREDENTIAL

    PS: I've known that we have another option that Login using Active Directory Password Authentication. But unfortunately, this will be used only for Configured Active Directory Admin alone.But in my organization, there are more than 100 members.So there is no way to give at least 10 members to use the Active Directory login

    Thanks in Advance,
    Jay

  • October 22, 2017 at 10:27 am

    #1964705

    It's a bug in SSMS older version, and this been solved in the new versions

    Please see here

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply