Merge lp:~ahasenack/charms/precise/landscape-client/client-charm-doc into lp:charms/landscape-client

Proposed by Andreas Hasenack
Status: Merged
Merged at revision: 29
Proposed branch: lp:~ahasenack/charms/precise/landscape-client/client-charm-doc
Merge into: lp:charms/landscape-client
Diff against target: 63 lines (+32/-4)
2 files modified
README (+24/-0)
config.yaml (+8/-4)
To merge this branch: bzr merge lp:~ahasenack/charms/precise/landscape-client/client-charm-doc
Reviewer Review Type Date Requested Status
James Page Approve
Darryl Weaver (community) Approve
Review via email: mp+191277@code.launchpad.net

Commit message

Explain in a bit more detail the ssl-public-key config option, and elaborate on the two url options we also have in there.

Description of the change

Explain in a bit more detail the ssl-public-key config option, and elaborate on the two url options we also have in there.

To post a comment you must log in.
Revision history for this message
Darryl Weaver (dweaver) wrote :

The instructions look good to me. I have followed them and tested the landscape-client charm works with these options.

review: Approve
Revision history for this message
James Page (james-page) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'README'
2--- README 2013-03-06 21:25:41 +0000
3+++ README 2013-10-15 19:13:53 +0000
4@@ -71,6 +71,30 @@
5 execute scripts. Keyword "ALL" can be used to include all users on the
6 system.
7
8+ssl-public-key:
9+ If needed, use this to give the client the CA certificate it should use to
10+ verify the server certificate it is connecting to.
11+
12+
13+When registering the client against a server with a custom or not well known
14+CA, you will need to use the ssl-public-key option. To insert the certificate
15+contents into the charm config directly, just encode it in base64.
16+
17+For example, let's assume ca.pem is a file with the CA certificate the client
18+needs to use to verify the server:
19+
20+$ cat ca.pem | openssl base64 -e > ca.encoded
21+
22+Now insert the ca.encoded contents into the charm config, like this:
23+
24+landscape-client:
25+ url: ....
26+ ping-url: ....
27+ ssl-public-key: |
28+ base64:<insert-here-
29+ contents-of-ca.encoded>...
30+ ...
31+ ...
32
33 Contact Information
34 ===================
35
36=== modified file 'config.yaml'
37--- config.yaml 2013-03-21 22:57:40 +0000
38+++ config.yaml 2013-10-15 19:13:53 +0000
39@@ -24,16 +24,20 @@
40 type: string
41 url:
42 description: |
43- The server URL to connect to.
44+ The message server URL to connect to. Normally
45+ https://fqdn/message-system.
46 type: string
47 ping-url:
48 description: |
49- The URL to perform lightweight exchange initiation with.
50+ The ping server URL to perform lightweight exchange initiation with.
51+ Normally http://fqdn/ping.
52 type: string
53 ssl-public-key:
54 description: |
55- The public SSL key to verify the server. Only used if
56- the given URL is https.
57+ The CA certificate to verify the server certificate with. This can be
58+ a path to a file, or a base64 encoded entry of the certificate itself,
59+ prefixed with "base64:". This config is only used if the message server
60+ URL given above starts with https.
61 type: string
62 server-autodiscover:
63 description: |

Subscribers

People subscribed via source and target branches