Installing latest Keyvault-Keys library through vcpkg results in linker errors to credential classes

[kyle-patterson]

Describe the bug
When installing keyvault-keys 4.0.0 through vcpkg, the linker will not find ClientSecretCredential or ManagedIdentityCredential.

Exception or Stack Trace
Exception when building:

unresolved external symbol "const Azure::Identity::ClientSecretCredential::`vftable'" (??_7ClientSecretCredential@Identity@Azure@@6b@) referenced in function "public: __cdecl Azure::Identity::ClientSecretCredential::ClientSecretCredential(class std::basic_string<char,struct std::char_traits,class std::allocator >,class std::basic_string<char,struct std::char_traits,class std::allocator >,class std::basic_string<char,struct std::char_traits,class std::allocator >,struct Azure::Core::Credentials::TokenCredentialOptions const &)" (??0ClientSecretCredential@Identity@Azure@@qeaa@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@00AEBUTokenCredentialOptions@Credentials@Core@2@@z)

Error LNK2019 unresolved external symbol "public: __cdecl Azure::Identity::ManagedIdentityCredential::ManagedIdentityCredential(class std::basic_string<char,struct std::char_traits,class std::allocator > const &,struct Azure::Core::Credentials::TokenCredentialOptions const &)" (??0ManagedIdentityCredential@Identity@Azure@@qeaa@AEBV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@AEBUTokenCredentialOptions@Credentials@Core@2@@z) referenced in function "void __cdecl std::_Construct_in_place<class Azure::Identity::ManagedIdentityCredential,char * &>(class Azure::Identity::ManagedIdentityCredential &,char * &)" (??$_Construct_in_place@VManagedIdentityCredential@Identity@Azure@@AEAPEAD@std@@YAXAEAVManagedIdentityCredential@Identity@Azure@@AEAPEAD@Z)

To Reproduce

1. install package: vcpkg install azure-security-keyvault-keys-cpp (any triplet)
2. In cmakelists:

add find_package(azure-security-keyvault-keys-cpp CONFIG REQUIRED)
target_link_libraries(main PRIVATE Azure::azure-security-keyvault-keys)

3. Generate cache and build

Setup (please complete the following information):

• OS: Windows 10, 64-bit
• IDE : Visual Studio 2019
• Version of the Library used: keys 4.0.0, identity 1.1.0, core 1.2.0

Additional context
Building from latest main resolves the issue, it seems to only be when installing through vcpkg. Additionally, explicitly linking to azure-identity (ie, target_link_libraries(main PRIVATE Azure::azure-identity)) will resolve ManagedIdentityCredential, but not ClientSecretCredential.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[vhvb1989]

Make sure azure-identity is also installed.

The linker is complaining about it can’t find the ClientSecretCredential which comes from azure-identity.

Identity is not a dependency of any other package (for building the library).

Identity becomes a dependency of the application where some service (like keyvault or storage) is used together with an specific credential.

[vhvb1989]

See how Key Vault samples are linking Identity as well like:

target_link_libraries(sample1-hello-world PRIVATE azure-security-keyvault-keys azure-identity)

[kyle-patterson]

The CMakeLists in question is already doing that:

#------in the root CMakeLists.txt

cmake_minimum_required (VERSION 3.8)

project ("azure-test")

find_package(azure-security-keyvault-keys-cpp CONFIG REQUIRED)
find_package(azure-identity-cpp CONFIG REQUIRED)

# Include sub-projects.
add_subdirectory ("azure-test")

#-------in the azure-test subdirectory CMakeLists.txt
add_executable (azure-test "azure-test.cpp" "azure-test.h")
target_link_libraries(azure-test PRIVATE Azure::azure-security-keyvault-keys Azure::azure-identity)

This helps when trying to link ManagedIdentityCredential, but I still get the ClientSecretCredential error

[vhvb1989]

Can you share the azure-test.cpp as well?

[vhvb1989]

And can you also share the output of running vcpkg.exe list from within the Vcpkg folder. I want to see what libraries are installed in there