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

Client Certificates Web API Support #5166

Merged
merged 1 commit into from
Feb 14, 2019

Conversation

kingthorin
Copy link
Member

@kingthorin kingthorin commented Dec 28, 2018

Builds on: #4892

Allow PCKS12 Client Certificate to be specified and enabled via the web
API.
Allow Client Certificate handling to be disabled via the web API.

Fixes #2023

@kingthorin
Copy link
Member Author

kingthorin commented Dec 28, 2018

Outstanding:

  • GUI - If Options > Client Certificate is visited, then a cert is enabled via the Web API, then the Options panel is re-opened you have to navigate away and back to Client Certificate to see the new details displayed.
  • API > Need to add a disable option web API endpoint? I tried this a few different ways and couldn't get it working (at least it was never disabled in the Options panel) [I ended up reverting the code as I couldn't seem to get it working].

@kingthorin kingthorin changed the title Client Certificates Web API Support WIP - Client Certificates Web API Support [DO NOT MERGE] Dec 28, 2018
@kingthorin
Copy link
Member Author

kingthorin commented Feb 1, 2019

Rebased current and fixed an issue with not setting the index param.

GUI - If Options > Client Certificate is visited, then a cert is enabled via the Web API, then the Options panel is re-opened you have to navigate away and back to Client Certificate to see the new details displayed.

I'm not sure that's a major issue, there seem to be other places within the options panels where API initiated changes aren't properly reflected in the GUI.

@kingthorin kingthorin force-pushed the client-cert-api branch 4 times, most recently from b99fab2 to df6b6cd Compare February 13, 2019 16:31
Allow PCKS12 Client Certificate to be specified and enabled via the web
API.
Allow Client Certificate handling to be disabled via the web API.

Fixes zaproxy#2023
@kingthorin kingthorin changed the title WIP - Client Certificates Web API Support [DO NOT MERGE] Client Certificates Web API Support Feb 14, 2019
@thc202
Copy link
Member

thc202 commented Feb 14, 2019

Thanks!

@psiinon psiinon merged commit 6d68f2b into zaproxy:develop Feb 14, 2019
@thc202
Copy link
Member

thc202 commented Feb 17, 2019

@kingthorin would you mind updating the release notes to mention the new API endpoints?

@kingthorin
Copy link
Member Author

Will do.

@kingthorin kingthorin self-assigned this Feb 17, 2019
@thc202
Copy link
Member

thc202 commented Feb 17, 2019

Thanks!

kingthorin added a commit to kingthorin/zap-core-help that referenced this pull request Feb 18, 2019
kingthorin added a commit to kingthorin/zap-core-help that referenced this pull request Feb 18, 2019
Follow-up to:
zaproxy#215
zaproxy/zaproxy#5166

In the API section I also removed two spurious spaces on the
setOptionAddQueryParam section.
@kingthorin kingthorin removed their assignment Feb 18, 2019
@lock
Copy link

lock bot commented Oct 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Oct 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

Allow to set client certificate (PKCS#12) through the ZAP API
3 participants