amazon-quicksight-embedding-sample
amazon-quicksight-embedding-sample copied to clipboard
amazon-archives
Pass JWT through to Lambda
The embedding requires a re-authentication every 10 hours. This means that from our UI the user has to put in their password to access a dashboard, frequently. Is there a way to pass the JWT from a web app that the user might already be logged into? This way the experience for end customers using our dashboard is better. They don't have to re-input their password to view different dashboards. They should just be able to log into our web app, see a list of available dashboards, then click on the one they want to view. Also, I think the embed URL will return faster this way.
For more context, we maintain a DB of dashboard records that have the ID. We have rule based auth on our server to control who can see dashboard objects in our DB from our web app.
Hi @Nomad-Go, one of the ways I can think of is by doing much of the Cognito related work in your front-end.
Most of the things here: https://github.com/aws-samples/amazon-quicksight-embedding-sample/blob/master/lambda/index.js#L81-L100 can be moved out of the lambda to your web app. The JWT token returned from the auth result can be stored in your browser (local storage, session storage or maybe even a cookie). So instead of making a call to the lambda with username or password, you can modify it by just passing the essentials required here: https://github.com/aws-samples/amazon-quicksight-embedding-sample/blob/master/lambda/index.js#L101-L110.
This way, you would not need to re-authenticate the user each time, but use the result of authentication (JWT token + session name) stored in the browser cache to fetch a new embed url. Hope this suggestion helps!
Ok great. This was the direction I was header. Could you help me clarify two things? First, I can't find API documentation for the amazon-cognito-identity-js module. I'm looking for an equivalent of the AWS JavaScript SDK API documentation.
Second, I want to clarify this line:
var sessionName = result.getIdToken().payload.sub;
Since I can't find the documentation for the amazon-cognito-identity-js module I just assume we are looking at the "subject" of the "claims" section of a JWT?
Check this page for details about amazon-cognito-identity-js.
The sub here refers to the userid of your cognito user. You could change it to the email if you want, or anything else that helps to uniquely identify a user. You can find the structure of the payload here under a section called ID Token Payload.
Let me know if these links help!
Roger. Thank you again for the clarification. I didn't realize that, that library was separate from the actual Javascript AWS SDK.
I know decoding a JWT is slightly involved. However, I could just pass the JWT and decode the sub out of the claims section rather then pass it though as a param? I know it's easily accessible from the SDK on the client side so why bother decoding it in the Lambda when you can just pass it. Unless there is some security risk in passing it as a param. Maybe instead of putting the JWT in the params I could to an Authorization: Bearer <JWT> header?
