Ahson Khan

KubectlExecuteIdentityAKSTests fails with System.InvalidOperationException: ERROR: AADSTS700024: Client assertion is not within its valid time range

1

From https://github.com/Azure/azure-sdk-for-net/pull/46135#issuecomment-2372527420 I keep seeing a seemingly unrelated test fail on [Ubuntu, leg Build & Test (all tests for net8.0) - Federated Auth](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4163699&view=logs&j=e08f9da5-dedf-508d-cb81-dc53e622c73b&t=96ffab2b-fe3c-5ce1-8cb5-7687a41af6c0) run from `net - identity - tests`:...

ApiVersion field within client options for keyvault secret, key, and settings need to be settable.

5

For some reason, these option fields are marked as `const` which means the user can't set them. They should likely be non-const. Making this change is non-breaking (unlike the other...

Make ApiVersion field within client options settable for keyvault packages

1

Fixes https://github.com/Azure/azure-sdk-for-cpp/issues/6126

If we really need to keep it, move the `#pragma once` after the license header https://github.com/Azure/azure-sdk-for-cpp/blob/22c52996f34099af7e1ef871cef45da29bc39c13/sdk/tables/azure-data-tables/test/ut/serializers_test.hpp#L1-L13

The `_detail` and `_internal` namespace should be the last one in the chain of namespace following SDK design precedence

7

We currently have types in headers that are in the `_detail` namespace which contain sub-namespaces like `Cryptography`. https://github.com/Azure/azure-sdk-for-cpp/blob/0e699e4c7a39078daba7d902f9ee9b5b98b1b5cf/sdk/tables/azure-data-tables/inc/azure/data/tables/internal/cryptography/url_encode.hpp#L12 The existing precedence in the SDK is that `_detail`/`_internal` is the last...

We currently have tables_clients.hpp (plural). Changing this after the GA would be considered breaking, so we'd want to fix it before https://github.com/Azure/azure-sdk-for-cpp/pull/6116 We have not made `client` plural in other...

As a package author, I should be able to GA release individual packages on vcpkg with confidence by having automated testing that detects potential build errors earlier based on package permutations

1

**The problem:** - We don't always GA or release all packages at the same time/milestone. Therefore, we need a mechanism of testing of shipping individual packages prior to the day...

There is a couple of assumptions within the ClientCertificateCredential implementation being made: - Assuming there is only one cert in the file (and that is the signing cert). - Assuming...

Improve end customer testing of acquiring packages that ship as beta, combined with other packages that are GA.

2

It is important for customers to be able to adopt our specific beta packages, easily, so they can provide valuable feedback on new features, while keeping the rest of the...

Support token cache persistence in client assertion workflow

1

**Description of Ask:** To have `ClientAssertionCredentialOptions` implement `ISupportsTokenCachePersistenceOptions`. As a consumer of Identity, Azure PowerShell is dependent on the Azure Identity library for .NET. Now the client assertion workflow has...