# Node Template using SAML tokens **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [June 30, 2020, 3:50am UTC](https://forums.suse.com/t/node-template-using-saml-tokens/17843 "2020-06-30T03:50:05Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Plenty](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Plenty](https://forums.suse.com/u/Plenty)\ **Post date:** [June 30, 2020, 3:50am UTC](https://forums.suse.com/t/node-template-using-saml-tokens/17843/1 "2020-06-30T03:50:05Z")
I can’t seem to authenticate using the node template’s aws access key and secret key. I am assuming that’s because I’m using a ADFS saml authentication. Some parts of rancher v2 uses the optional aws session token (e.g. when adding an aws eks cluster) which supports this type of authentication. Is there a work around for node template to use temporary auths? Use case, I can’t create a RKE amazon ec2 cluster using Rancher because it requires a node template and I can’t authenticate the node template using my temp saml credentials. ---
**Author:** ![cjellick](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cjellick/32/2876_2.png) [@cjellick](https://forums.suse.com/u/cjellick)\ **Post date:** [June 30, 2020, 5:36pm UTC](https://forums.suse.com/t/node-template-using-saml-tokens/17843/2 "2020-06-30T17:36:16Z")
Our RKE amazon ec2 unfortunately only supports the “old school” access/secret keys. It just doesnt have support for session keys. You can see details in this issue: > > > Rancher Amazon EC2 Node Template doesn't support Temporary AWS AccessKey & SecretKey with session token: > https://docs.aws.amazon.com/IAM/latest/UserGuide/id\_credentials\_temp\_use-resources.html ---
**Author:** ![Plenty](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Plenty](https://forums.suse.com/u/Plenty)\ **Post date:** [July 1, 2020, 2:04am UTC](https://forums.suse.com/t/node-template-using-saml-tokens/17843/3 "2020-07-01T02:04:22Z")
Got it, thanks for the information.