You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [Spring Auto Reconfiguration](docs/framework-spring_auto_reconfiguration.md) ([Configuration](docs/framework-spring_auto_reconfiguration.md#configuration))
Copy file name to clipboardExpand all lines: docs/framework-protect_app_security_provider.md
+23-27Lines changed: 23 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# ProtectApp Security Provider Framework
2
-
The ProtectApp Security Provider Framework causes an application to be automatically configured to work with a bound [ProtectApp Security Service][].
2
+
The ProtectApp Security Provider Framework causes an application to be automatically configured to work with a bound [ProtectApp Security Service][].
3
3
4
4
<table>
5
5
<tr>
@@ -20,65 +20,61 @@ When binding to the ProtectApp Security Provider using a user-provided service,
20
20
| Name | Description
21
21
| ---- | -----------
22
22
| `client` | The client configuration
23
-
| `trustedcerts` | An array of certs containing trust information
23
+
| `trusted_certificates` | An array of certs containing trust information
24
24
| `NAE_IP.1` | A list of KeySecure server ips or hostnames to be used
25
25
| `***` | (Optional) Any additional entries will be applied as a system property appended to `-Dcom.ingrian.security.nae.` to allow full configuration of the library.
26
26
27
-
28
27
#### Client Configuration
29
28
| Name | Description
30
29
| ---- | -----------
31
30
| `certificate` | A PEM encoded client certificate
32
-
| `private-key` | A PEM encoded client private key
31
+
| `private_key` | A PEM encoded client private key
Note the client portion is very exacting and needs line breaks in the body every 64 characters.
66
61
67
-
1. The file must contain:
68
-
-----BEGIN CERTIFICATE-----
69
-
on a separate line (i.e. it must be terminated with a newline).
70
-
2. Each line of "gibberish" must be 64 characters wide.
71
-
3. The file must end with:
72
-
-----END CERTIFICATE-----
73
-
and also be terminated with a newline.
74
-
4. Don't save the cert text with Word. It must be in ASCII.
75
-
5. Don't mix DOS and UNIX style line terminations.
62
+
1. The file must contain:
63
+
`-----BEGIN CERTIFICATE-----`
64
+
on a separate line (i.e. it must be terminated with a newline).
65
+
1. Each line of "gibberish" must be 64 characters wide.
66
+
1. The file must end with:
67
+
`-----END CERTIFICATE-----`
68
+
and also be terminated with a newline.
69
+
1. Don't save the cert text with Word. It must be in ASCII.
70
+
1. Don't mix DOS and UNIX style line terminations.
76
71
77
72
So, here are a few steps you can take to normalize your certificate:
78
-
1. Run it through dos2unix
79
-
dos2unix cert.pem
80
-
2. Run it through fold
81
-
fold -w 64 cert.pem
73
+
74
+
1. Run it through `dos2unix`
75
+
`$ dos2unix cert.pem`
76
+
1. Run it through `fold`
77
+
`$ fold -w 64 cert.pem`
82
78
83
79
## Configuration
84
80
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to [Configuration and Extension][].
@@ -91,7 +87,7 @@ The framework can be configured by modifying the [`config/protect_app_security_p
91
87
| `version` | Version of the ProtectApp Security Provider to use.
92
88
93
89
### Additional Resources
94
-
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.
90
+
The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the `resources/protect_app_security_provider` directory in the buildpack fork.
0 commit comments