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.

Sign up for GitHub

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

Jump to bottom

Allow cmdlets to use default cert/keys #41

Closed
codyhosterman opened this issue Dec 5, 2020 · 1 comment
Closed

Allow cmdlets to use default cert/keys #41

codyhosterman opened this issue Dec 5, 2020 · 1 comment
Assignees
@codyhosterman
Labels
enhancement New feature or request
Projects
1.4.2.0

Comments

@codyhosterman
Copy link
Contributor

With the 1.4.x.x release there is a new default cert/key feature. The cmdlets should be enhanced to not require a cert or private key if the default is desired. Cmdlets:

Get-PureOnePublicKey, New-PureOneJwt, New-PureOneConnection
@codyhosterman codyhosterman self-assigned this Dec 5, 2020
@codyhosterman codyhosterman added the enhancement New feature or request label Dec 5, 2020
@codyhosterman codyhosterman added this to To do in 1.4.2.0 via automation Dec 5, 2020
@codyhosterman codyhosterman moved this from To do to Done in 1.4.2.0 Dec 5, 2020
@codyhosterman
Copy link
Contributor Author

This is complete ins 1.4.2.0 with help examples added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@codyhosterman codyhosterman

Labels
enhancement New feature or request
Projects
No open projects
1.4.2.0
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@codyhosterman