Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

PhantomJS should support user certificates (*.pem, *.pfx) #10524

Closed
ariya opened this issue May 4, 2012 · 31 comments
Closed

PhantomJS should support user certificates (*.pem, *.pfx) #10524

ariya opened this issue May 4, 2012 · 31 comments

Comments

@ariya
Copy link
Owner

ariya commented May 4, 2012

frst...@googlemail.com commented:

Which version of PhantomJS are you using? Tip: run 'phantomjs --version'.
1.5

What steps will reproduce the problem?

  1. Open any webpage which requires user authentication via a user certificate (instead of login + password).
    2.
    3.

What is the expected output? What do you see instead?
Expected: One should be able to configure a file which stores the user certificate
Instead: The API doesn't provide this functionality

Which operating system are you using?
WinXP, Linux

Did you use binary PhantomJS or did you compile it from source?
Binary (on both OS)

Please provide any additional information below.
If the user has more than one applicable certificate in his/her certificate store the major web browsers start a dialog to select a certificate.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #524.
🌟   11 people had starred this issue at the time of migration.

@ariya
Copy link
Owner Author

ariya commented Sep 14, 2012

GBara...@demonwaremail.net commented:

'd say pem format is more user friendly for everyone on unix systems, but it would be nice if both can be specified as pkcs12 is better supported on windows.

I think we also need an option to specify the CA chain. Normally for PEM format we need:

--private-key-file
--ssl-certificate-file
--ca-certficate-file

Also, many people would be worried about specifying the passphase in the command line (bash history will reveal the passphrase).
so, in addition to the passphrase in the command line:

  • read the file from stdin
  • specify a file with the passphrase.

And since we're specifying all that stuff in the command line, maybe phantomjs could also read these options from a default "~/.phantomjs.conf", or we can specify the config file in the command line as most unix utilities do. Of course, the cmd options override config file options.

What do you think?

@raynor08
Copy link

rayno...@gmail.com commented:

Read all those from phantomJS's config sounds good to me. And hope this can be supported soon!

@ariya
Copy link
Owner Author

ariya commented Mar 1, 2013

mark.sto...@gmail.com commented:

I'd also like support for ".phantomjs.conf", so I don't have to enter --webdriver=4445 every time I launch it.

@passionke
Copy link

Hope this can be supported soon!!!!, I have the same question。

@mindscratch
Copy link

I also need support for using user certificates.

@nebulade
Copy link

+1

I would also need this feature.

@nil3
Copy link

nil3 commented Aug 26, 2013

Linking issue #11275 (with patch)

@cphoover
Copy link

cphoover commented Oct 8, 2013

+1 bump

@BulbITOrg
Copy link

+1 vote.

@offlinehacker
Copy link

+1

@Arno-v
Copy link

Arno-v commented Dec 18, 2013

+1 vote

@scott2449
Copy link

The other problem with this issue is that without CA cert support (alternative using ignore ssl errors) phantom then removes all the secure cookies from the text file when phantom.exit() is called. The work around is to copy the cookies file using fs before exit and then copy it back externally before running phantom again or (worse) don't use exit() in your script and sigkill the process.

@mindscratch
Copy link

any update or thoughts on this?

@simonflk
Copy link

+1

1 similar comment
@apergy
Copy link

apergy commented Feb 13, 2014

+1

@nathanmesserbbc
Copy link

This is something that we need as well.

Has anyone who knows the phantomjs codebase had a look at the patch here to see if it's suitable?

https://github.com/ffray/phantomjs/tree/ssl-client-auth

@subvertnormality
Copy link

+1

6 similar comments
@danielabar
Copy link

+1

@herve-odiard
Copy link

+1

@franck34
Copy link

+1

@pfuerholz
Copy link

+1

@dblooman
Copy link

+1

@ghost
Copy link

ghost commented Oct 11, 2014

+1

@dblooman
Copy link

Will this be supported in 2.0?

@agustinf
Copy link

agustinf commented Dec 2, 2014

+1 😢

@smoelker
Copy link

+1

2 similar comments
@surebert
Copy link

+1

@adriannier
Copy link

+1

@vitallium
Copy link
Collaborator

Implemented in 54a54dc!

@pabrrs
Copy link

pabrrs commented Aug 12, 2017

+1

1 similar comment
@avandrevitor
Copy link

+1

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

No branches or pull requests