Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help with a new provider? #8

Open
deinspanjer opened this issue Aug 22, 2016 · 3 comments
Open

Help with a new provider? #8

deinspanjer opened this issue Aug 22, 2016 · 3 comments

Comments

@deinspanjer
Copy link

I've spent too long now trying to get a Google for Work SAML provider working with this.

Using docs on the web, I was able to get SSO going without too much trouble and can use it to open the AWS console from a real browser, but I just haven't been able to get Nightmare to be able to do the full authentication path.

I was hoping someone might be able to take a look at this non-working code and give me any tips?

https://github.com/deinspanjer/aws-sts/blob/d7a6891c366346fdcf6f413db6a8442f333d20e6/src/providers/gfw.js

@bromanko
Copy link
Contributor

Where does the full authentication path fail?

@deinspanjer
Copy link
Author

It doesn't seem to notice when the second page that asks for the password has loaded. It just returns an error saying that Cannot read property 'blur' of null

@bromanko
Copy link
Contributor

It's likely that the wait command is waiting on something that doesn't change or ever load. For instance, this wait on body could be falsely indicating the next page has loaded if all modifications to the DOM happen client side (no page refresh). If Nightmare can't find the password field to attach the handler I could see an error like above being generated. Try a different wait condition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants