Skip to content

ProtectApp Security Provider Release#385

Closed
chrisjdhanley wants to merge 1 commit into
cloudfoundry:masterfrom
chrisjdhanley:master
Closed

ProtectApp Security Provider Release#385
chrisjdhanley wants to merge 1 commit into
cloudfoundry:masterfrom
chrisjdhanley:master

Conversation

@chrisjdhanley
Copy link
Copy Markdown
Contributor

No description provided.

@cfdreddbot
Copy link
Copy Markdown

Hey chrisjdhanley!

Thanks for submitting this pull request!

All pull request submitters and commit authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate).

When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization.

If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions.

Once you've publicized your membership, one of the owners of this repository can close and reopen this pull request, and dreddbot will take another look.

@nebhale nebhale self-requested a review February 21, 2017 22:11
@nebhale nebhale self-assigned this Feb 21, 2017
@nebhale nebhale added this to the v3.14 milestone Feb 21, 2017
Copy link
Copy Markdown
Contributor

@nebhale nebhale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as the code changes go, nothing major. Please squash all the commits to a single one.

The big issue is that it seems like the dependency can't yet be downloaded. I'm going to hold off merging until it is available.

# Configuration for the ProtectApp Security Provider framework
---
version: 8.4.+
repository_root: http://files.cf-hsm.io/protectapp-installer
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While the index.yml is now in place, the file that it points to doesn't exist yet (or the index is wrong).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

index.yml was wrong. Should be updated tommorrow

In order to create the credentials payload, you should collapse the JSON payload to a single line and set it like the following

```
$ cf create-user-provided-service protectapp -p '{"client":{"certificate":"-----BEGIN CERTIFICATE-----\n....\n-----END CERTIFICATE-----","private-key":"-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----\n"},"trustedcerts":{"-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----"},NAE_IP.1":"172.17.34.100"}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

trustedcerts is an array, not a hash.

| `version` | Version of the ProtectApp Security Provider to use.

### Additional Resources
The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the `resources/protectapp_security_provider` directory in the buildpack fork.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be resources/protect_app_security_provider.

## Configuration
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to [Configuration and Extension][].

The framework can be configured by modifying the [`config/protectapp_security_provider.yml`][] file in the buildpack. The framework uses the [`Repository` utility support][repositories] and so it supports the [version syntax][] defined there.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be config/protect_app_security_provider.yml

### Additional Resources
The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the `resources/protectapp_security_provider` directory in the buildpack fork.

[`config/protectapp_security_provider.yml`]: ../config/protectapp_security_provider.yml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be config/protect_app_security_provider.yml

@chrisjdhanley
Copy link
Copy Markdown
Contributor Author

All the other changes were made, I'll send a note when I get the index.yml fixed.

| `version` | Version of the ProtectApp Security Provider to use.

### Additional Resources
The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the `resources/pprotect_app_security_provider` directory in the buildpack fork.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pprotect_app... I'll get it when I do the polishing.

nebhale pushed a commit that referenced this pull request Feb 22, 2017
This change adds support for the ProtectApp Security Provider service.

[#385]
nebhale added a commit that referenced this pull request Feb 22, 2017
This change polishes up the contribution to be a bit more idomatic for the
project.

[#385]
nebhale added a commit that referenced this pull request Feb 23, 2017
This change polishes up the contribution to be a bit more idomatic for the
project.

[#385]
nebhale added a commit that referenced this pull request Feb 24, 2017
This change polishes up the contribution to be a bit more idomatic for the
project.

[#385]
@nebhale nebhale closed this in 24f60ad Feb 24, 2017
ramonskie pushed a commit that referenced this pull request Dec 4, 2025
This change adds support for the ProtectApp Security Provider service.

[#385]
ramonskie pushed a commit that referenced this pull request Dec 4, 2025
This change polishes up the contribution to be a bit more idomatic for the
project.

[#385]
ramonskie pushed a commit that referenced this pull request Dec 4, 2025
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

Successfully merging this pull request may close these issues.

3 participants