When using gremlin-aws-sigv4 with temporary credentials (e.g., in a lambda), I expect to be able to provide the session token and have it included in the signed request so that I can authenticate correctly.
Actual behavior
The session token is not considered by gremlin-aws-sigv4 and therefore authenticated requests are not possible using temporary credentials.
Steps to reproduce the behavior
Create a Neptune DB with IAM authentication enabled.
Create a lambda with an execution role allowing access to the database.
Use gremlin-aws-sigv4 to make a request to the database,
Note that you get a 403 Not Authorized error response from the database.
Expected behavior
When using
gremlin-aws-sigv4
with temporary credentials (e.g., in a lambda), I expect to be able to provide the session token and have it included in the signed request so that I can authenticate correctly.Actual behavior
The session token is not considered by
gremlin-aws-sigv4
and therefore authenticated requests are not possible using temporary credentials.Steps to reproduce the behavior
gremlin-aws-sigv4
to make a request to the database,