-
Notifications
You must be signed in to change notification settings - Fork 40
Cannot parse form field #11
Comments
I'm running into the same issue - I wonder if this is because we're using ADFS3? I'm using the same details I use for the (modified) version of https://aws.amazon.com/blogs/security/how-to-implement-federated-api-and-cli-access-using-saml-2-0-and-ad-fs/ |
@AMMullan could you please answer the question I asked @jcwhisman ? If form-based login isn't your default configuration, this will not work as only forms-based login is supported. |
Hey @JordonPhillips - yeah, we use form-based logins. I'm just working through comparing what awsprocesscreds does to process the form and how it differs to the way I do it, might just be a small difference. |
I am struggeling with ADFS too. Part 1 is working if I use
Then I get access keys. For other problems, I will open a different issue. |
Yep, I replicated the fix @hoegertn proposed and it works. |
I ran into the same issue and the fix by @hoegertn solves at least the part about logging in. I struggled a bit to figure out where to apply it so I am including a diff:
Perhaps it is an idea if these field names can be passed as arguments to the While I am able to login now, I am running into a problem where I am not able to switch roles but I'll open a separate issue for that. |
Same problem here, and changing fields to 'UserName' and 'Password' helps. Would it be silly to support all conventions seen in the codebase and have it choose the appropriate one based on what is found in the form?
|
is there an update for that issue? this issue is still present in 2019 if the authentication is done using NTLM instead of username/password. |
I'm still seeing this issue. I pulled from pip, and When I change the Is there an alternate authentication approach I should be looking at? |
I'm also facing the same issue, but after doing the fix as mentioned in the above comments, I am not getting prompt for password but instead getting below error:
|
Copy awslabs#11 - add multiple form field names for use with different ADFS versions
I am attempting to run the following line:
awsprocesscreds-saml --endpoint https://my.company.com/adfs/ls/IdpInitiatedSignOn.aspx?loginToRp=urn:amazon:webservices --username '[email protected] --provider adfs --role-arn arn:aws:iam::595513102389:role/IaaSOperations --verbose
I am getting the following error:
The text was updated successfully, but these errors were encountered: