Quicksight.describeUser fails when an encodable username is used

[pedromdias]

There seems to be a bug with the Async client due to the encoding of the username as part of the request.

Steps to reproduce:

• (OPTIONAL) Register a user to quicksight via email - eg. "some@email.com"
• Instantiate a QuickSightAsyncClient
• call describeUser() with: a valid "awsAccountId", "namespace" being "default" and pass an email (eg. "some@email.com") as "userName" (regardless of whether it exists or not).
• Await for the future completion

StatusQuo: An exception is thrown "QuickSightException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."
ExpectedResult: Successful future if user exists, or "ResourceNotFoundException" if user does not exist.

val quicksight: QuickSightAsyncClient = AkkaHttpClient
    .builder()
    .withActorSystem(system)
    .withConnectionPoolSettings(
      ConnectionPoolSettings(system)
        .withMaxConnections(15)
        .withIdleTimeout(15.seconds)
    )
quicksight
      .describeUser(_.awsAccountId("ACCOUNT_ID")
        .userName("USER_NAME_AS_EMAIL")
        .namespace("default"))

The same applies to the deleteUser, but not to the registerUser.
It seems to be that some encoding is happening to the username (which is part of the path in delete/describe) and when that changes the username (as is the case with an email), it leads to the exception in question.

If a simple username is used (eg. "myname"), it will work fine.

PS: I initially file this in the sdk repo. Feel free to check it out for further information.

[matsluni]

Hi @pedromdias, thanks for the report.

I haven't seen such an issue before. I'll try to investigate on my end, but I am currently short on time, so I can't promise quick results.

[matsluni]

@pedromdias I investigated this and opened another issue here: aws/aws-sdk-java-v2#3154