forked from freeipa/freeipa
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdogtag.py
1701 lines (1399 loc) · 63.7 KB
/
dogtag.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# Authors:
# Ade Lee <alee@redhat.com>
# Andrew Wnuk <awnuk@redhat.com>
# Jason Gerard DeRose <jderose@redhat.com>
# Rob Crittenden <rcritten@@redhat.com>
# John Dennis <jdennis@redhat.com>
# Fraser Tweedale <ftweedal@redhat.com>
# Abhijeet Kasurde <akasurde@redhat.com>
#
# Copyright (C) 2014-2016 Red Hat, Inc.
# see file 'COPYING' for use and warranty information
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
r'''
==============================================
Backend plugin for RA using Dogtag (e.g. CMS)
==============================================
Overview of interacting with CMS:
---------------------------------
CMS stands for "Certificate Management System". It has been released under a
variety of names, the open source version is called "dogtag".
IPA now uses the REST API provided by dogtag, as documented at
https://github.com/dogtagpki/pki/wiki/REST-API
The below is still relevant in places, particularly with data handling.
This history of Javascript parsing and using the optional XML is left
for historical purposes and for the last-used xml-based call that
IPA makes (updateCRL).
CMS consists of a number of servlets which in rough terms can be thought of as
RPC commands. A servlet is invoked by making an HTTP request to a specific URL
and passing URL arguments. Normally CMS responds with an HTTP response consisting
of HTML to be rendered by a web browser. This HTTP HTML response has both
Javascript SCRIPT components and HTML rendering code. One of the Javascript
SCRIPT blocks holds the data for the result. The rest of the response is derived
from templates associated with the servlet which may be customized. The
templates pull the result data from Javascript variables.
One way to get the result data is to parse the HTML looking for the Javascript
variable initializations. Simple string searches are not a robust method. First of
all one must be sure the string is only found in a Javascript SCRIPT block and
not somewhere else in the HTML document. Some of the Javascript variable
initializations are rather complex (e.g. lists of structures). It would be hard
to correctly parse such complex and diverse Javascript. Existing Javascript
parsers are not generally available. Finally, it's important to know the
character encoding for strings. There is a somewhat complex set of precedent
rules for determining the current character encoding from the HTTP header,
meta-equiv tags, mime Content-Type and charset attributes on HTML elements. All
of this means trying to read the result data from a CMS HTML response is
difficult to do robustly.
However, CMS also supports returning the result data as a XML document
(distinct from an XHTML document which would be essentially the same as
described above). There are a wide variety of tools to robustly parse
XML. Because XML is so well defined things like escapes, character encodings,
etc. are automatically handled by the tools.
Thus we never try to parse Javascript, instead we always ask CMS to return us an
XML document by passing the URL argument xml="true". The body of the HTTP
response is an XML document rather than HTML with embedded Javascript.
To parse the XML documents we use the Python lxml package which is a Python
binding around the libxml2 implementation. libxml2 is a very fast, standard
compliant, feature full XML implementation. libxml2 is the XML library of choice
for many projects. One of the features in lxml and libxml2 that is particularly
valuable to us is the XPath implementation. We make heavy use of XPath to find
data in the XML documents we're parsing.
Parse Results vs. IPA command results:
--------------------------------------
CMS results can be parsed from either HTML or XML. CMS unfortunately is not
consistent with how it names items or how it utilizes data types. IPA has strict
rules about data types. Also IPA would like to see a more consistent view CMS
data. Therefore we split the task of parsing CMS results out from the IPA
command code. The parse functions normalize the result data by using a
consistent set of names and data types. The IPA command only deals with the
normalized parse results. This also allow us to use different parsers if need be
(i.e. if we had to parse Javascript for some reason). The parse functions
attempt to parse as must information from the CMS result as is possible. It puts
the parse result into a dict whose normalized key/value pairs are easy to
access. IPA commands do not need to return all the parsed results, it can pick
and choose what it wants to return in the IPA command result from the parse
result. It also rest assured the values in the parse result will be the correct
data type. Thus the general sequence of steps for an IPA command talking to CMS
are:
#. Receive IPA arguments from IPA command
#. Formulate URL with arguments for CMS
#. Make request to CMS server
#. Extract XML document from HTML body returned by CMS
#. Parse XML document using matching parse routine which returns response dict
#. Extract relevant items from parse result and insert into command result
#. Return command result
Serial Numbers:
---------------
Serial numbers are integral values of any magnitude because they are based on
ASN.1 integers. CMS uses the Java BigInteger to represent these. Fortunately
Python also has support for big integers via the Python long() object. Any
BigIntegers we receive from CMS as a string can be parsed into a Python long
without loss of information.
However Python has a neat trick. It normally represents integers via the int
object which internally uses the native C long type. If you create an int
object by passing the int constructor a string it will check the magnitude of
the value. If it would fit in a C long then it returns you an int
object. However if the value is too big for a C long type then it returns you
a Python long object instead. This is a very nice property because it's much
more efficient to use C long types when possible (e.g. Python int), but when
necessary you'll get a Python long() object to handle large magnitude
values. Python also nicely handles type promotion transparently between int
and long objects. For example if you multiply two int objects you may get back
a long object if necessary. In general Python int and long objects may be
freely mixed without the programmer needing to be aware of which type of
integral object is being operated on.
The leads to the following rule, always parse a string representing an
integral value using the int() constructor even if it might have large
magnitude because Python will return either an int or a long automatically. By
the same token don't test for type of an object being int exclusively because
it could either be an int or a long object.
Internally we should always being using int or long object to hold integral
values. This is because we should be able to compare them correctly, be free
from concerns about having the know the radix of the string, perform
arithmetic operations, and convert to string representation (with correct
radix) when necessary. In other words internally we should never handle
integral values as strings.
However, the XMLRPC transport cannot properly handle a Python long object. The
XMLRPC encoder upon seeing a Python long will test to see if the value fits
within the range of an 32-bit integer, if so it passes the integer parameter
otherwise it raises an Overflow exception. The XMLRPC specification does
permit 64-bit integers (e.g. i8) and the Python XMLRPC module could allow long
values within the 64-bit range to be passed if it were patched, however this
only moves the problem, it does not solve passing big integers through
XMLRPC. Thus we must always pass big integers as a strings through the XMLRPC
interface. But upon receiving that value from XMLRPC we should convert it back
into an int or long object. Recall also that Python will automatically perform
a conversion to string if you output the int or long object in a string context.
Radix Issues:
-------------
CMS uses the following conventions: Serial numbers are always returned as
hexadecimal strings without a radix prefix. When CMS takes a serial number as
input it accepts the value in either decimal or hexadecimal utilizing the radix
prefix (e.g. 0x) to determine how to parse the value.
IPA has adopted the convention that all integral values in the user interface
will use base 10 decimal radix.
Basic rules on handling these values
1. Reading a serial number from CMS requires conversion from hexadecimal
by converting it into a Python int or long object, use the int constructor:
serial_number = int(serial_number, 16)
2. Big integers passed to XMLRPC must be decimal unicode strings
unicode(serial_number)
3. Big integers received from XMLRPC must be converted back to int or long
objects from the decimal string representation.
serial_number = int(serial_number)
Xpath pattern matching on node names:
-------------------------------------
There are many excellent tutorial on how to use xpath to find items in an XML
document, as such there is no need to repeat this information here. However,
most xpath tutorials make the assumption the node names you're searching for are
fixed. For example:
doc.xpath('//book/chapter[*]/section[2]')
Selects the second section of every chapter of the book. In this example the
node names 'book', 'chapter', 'section' are fixed. But what if the XML document
embedded the chapter number in the node name, for example 'chapter1',
'chapter2', etc.? (If you're thinking this would be incredibly lame, you're
right, but sadly people do things like this). Thus in this case you can't use
the node name 'chapter' in the xpath location step because it's not fixed and
hence won't match 'chapter1', 'chapter2', etc. The solution to this seems
obvious, use some type of pattern matching on the node name. Unfortunately this
advanced use of xpath is seldom discussed in tutorials and it's not obvious how
to do it. Here are some hints.
Use the built-in xpath string functions. Most of the examples illustrate the
string function being passed the text *contents* of the node via '.' or
string(.). However we don't want to pass the contents of the node, instead we
want to pass the node name. To do this use the name() function. One way we could
solve the chapter problem above is by using a predicate which says if the node
name begins with 'chapter' it's a match. Here is how you can do that.
doc.xpath("//book/*[starts-with(name(), 'chapter')]/section[2]")
The built-in starts-with() returns true if its first argument starts with its
second argument. Thus the example above says if the node name of the second
location step begins with 'chapter' consider it a match and the search
proceeds to the next location step, which in this example is any node named
'section'.
But what if we would like to utilize the power of regular expressions to perform
the test against the node name? In this case we can use the EXSLT regular
expression extension. EXSLT extensions are accessed by using XML
namespaces. The regular expression name space identifier is 're:' In lxml we
need to pass a set of namespaces to XPath object constructor in order to allow
it to bind to those namespaces during its evaluation. Then we just use the
EXSLT regular expression match() function on the node name. Here is how this is
done:
regexpNS = "http://exslt.org/regular-expressions"
find = etree.XPath("//book/*[re:match(name(), '^chapter(_\d+)$')]/section[2]",
namespaces={'re':regexpNS}
find(doc)
What is happening here is that etree.XPath() has returned us an evaluator
function which we bind to the name 'find'. We've passed it a set of namespaces
as a dict via the 'namespaces' keyword parameter of etree.XPath(). The predicate
for the second location step uses the 're:' namespace to find the function name
'match'. The re:match() takes a string to search as its first argument and a
regular expression pattern as its second argument. In this example the string
to search is the node name of the location step because we called the built-in
node() function of XPath. The regular expression pattern we've passed says it's
a match if the string begins with 'chapter' is followed by any number of
digits and nothing else follows.
'''
from __future__ import absolute_import
import json
import logging
from lxml import etree
import time
import contextlib
import six
from ipalib import Backend, api, x509
from ipapython.dn import DN
import ipapython.cookie
from ipapython import dogtag, ipautil
from ipaserver.masters import find_providing_server
import pki
from pki.client import PKIConnection
import pki.crypto as cryptoutil
from pki.kra import KRAClient
if six.PY3:
unicode = str
logger = logging.getLogger(__name__)
# These are general status return values used when
# CMSServlet.outputError() is invoked.
CMS_SUCCESS = 0
CMS_FAILURE = 1
CMS_AUTH_FAILURE = 2
# CMS (Certificate Management System) status return values
# These are requestStatus return values used with templates
CMS_STATUS_UNAUTHORIZED = 1
CMS_STATUS_SUCCESS = 2
CMS_STATUS_PENDING = 3
CMS_STATUS_SVC_PENDING = 4
CMS_STATUS_REJECTED = 5
CMS_STATUS_ERROR = 6
CMS_STATUS_EXCEPTION = 7
def cms_request_status_to_string(request_status):
'''
:param request_status: The integral request status value
:return: String name of request status
'''
return {
1 : 'UNAUTHORIZED',
2 : 'SUCCESS',
3 : 'PENDING',
4 : 'SVC_PENDING',
5 : 'REJECTED',
6 : 'ERROR',
7 : 'EXCEPTION',
}.get(request_status, "unknown(%d)" % request_status)
def get_request_status_xml(doc):
'''
:param doc: The root node of the xml document to parse
:returns: request status as an integer
Returns the request status from a CMS operation. May be one of:
- CMS_STATUS_UNAUTHORIZED = 1
- CMS_STATUS_SUCCESS = 2
- CMS_STATUS_PENDING = 3
- CMS_STATUS_SVC_PENDING = 4
- CMS_STATUS_REJECTED = 5
- CMS_STATUS_ERROR = 6
- CMS_STATUS_EXCEPTION = 7
CMS will often fail to return requestStatus when the status is
SUCCESS. Therefore if we fail to find a requestStatus field we default the
result to CMS_STATUS_SUCCESS.
'''
request_status = doc.xpath('//xml/fixed/requestStatus[1]')
if len(request_status) == 1:
request_status = int(request_status[0].text)
else:
# When a request is successful CMS often omits the requestStatus
request_status = CMS_STATUS_SUCCESS
# However, if an error string was returned it's an error no
# matter what CMS returned as requestStatus.
# Just to make life interesting CMS sometimes returns an empty error string
# when nothing wrong occurred.
error_detail = doc.xpath('//xml/fixed/errorDetails[1]')
if len(error_detail) == 1 and len(error_detail[0].text.strip()) > 0:
# There was a non-empty error string, if the status was something
# other than error or exception then force it to be an error.
if not (request_status in (CMS_STATUS_ERROR, CMS_STATUS_EXCEPTION)):
request_status = CMS_STATUS_ERROR
return request_status
def parse_error_template_xml(doc):
'''
:param doc: The root node of the xml document to parse
:returns: result dict
CMS currently returns errors via XML as either a "template" document
(generated by CMSServlet.outputXML() or a "response" document (generated by
CMSServlet.outputError()).
This routine is used to parse a "template" style error or exception
document.
This routine should be use when the CMS requestStatus is ERROR or
EXCEPTION. It is capable of parsing both. A CMS ERROR occurs when a known
anticipated error condition occurs (e.g. asking for an item which does not
exist). A CMS EXCEPTION occurs when an exception is thrown in the CMS server
and it's not caught and converted into an ERROR. Think of EXCEPTIONS as the
"catch all" error situation.
ERROR's and EXCEPTIONS's both have error message strings associated with
them. For an ERROR it's errorDetails, for an EXCEPTION it's
unexpectedError. In addition an EXCEPTION may include an array of additional
error strings in it's errorDescription field.
After parsing the results are returned in a result dict. The following
table illustrates the mapping from the CMS data item to what may be found in
the result dict. If a CMS data item is absent it will also be absent in the
result dict.
+----------------+---------------+------------------+---------------+
|cms name |cms type |result name |result type |
+================+===============+==================+===============+
|requestStatus |int |request_status |int |
+----------------+---------------+------------------+---------------+
|errorDetails |string |error_string [1]_ |unicode |
+----------------+---------------+------------------+---------------+
|unexpectedError |string |error_string [1]_ |unicode |
+----------------+---------------+------------------+---------------+
|errorDescription|[string] |error_descriptions|[unicode] |
+----------------+---------------+------------------+---------------+
|authority |string |authority |unicode |
+----------------+---------------+------------------+---------------+
.. [1] errorDetails is the error message string when the requestStatus
is ERROR. unexpectedError is the error message string when
the requestStatus is EXCEPTION. This routine recognizes both
ERROR's and EXCEPTION's and depending on which is found folds
the error message into the error_string result value.
'''
response = {}
response['request_status'] = CMS_STATUS_ERROR # assume error
request_status = doc.xpath('//xml/fixed/requestStatus[1]')
if len(request_status) == 1:
request_status = int(request_status[0].text)
response['request_status'] = request_status
error_descriptions = []
for description in doc.xpath('//xml/records[*]/record/errorDescription'):
error_descriptions.append(etree.tostring(description, method='text',
encoding=unicode).strip())
if len(error_descriptions) > 0:
response['error_descriptions'] = error_descriptions
authority = doc.xpath('//xml/fixed/authorityName[1]')
if len(authority) == 1:
authority = etree.tostring(authority[0], method='text',
encoding=unicode).strip()
response['authority'] = authority
# Should never get both errorDetail and unexpectedError
error_detail = doc.xpath('//xml/fixed/errorDetails[1]')
if len(error_detail) == 1:
error_detail = etree.tostring(error_detail[0], method='text',
encoding=unicode).strip()
response['error_string'] = error_detail
unexpected_error = doc.xpath('//xml/fixed/unexpectedError[1]')
if len(unexpected_error) == 1:
unexpected_error = etree.tostring(unexpected_error[0], method='text',
encoding=unicode).strip()
response['error_string'] = unexpected_error
return response
def parse_updateCRL_xml(doc):
'''
:param doc: The root node of the xml document to parse
:returns: result dict
:except ValueError:
After parsing the results are returned in a result dict. The following
table illustrates the mapping from the CMS data item to what may be found
in the result dict. If a CMS data item is absent it will also be absent in
the result dict.
If the requestStatus is not SUCCESS then the response dict will have the
contents described in `parse_error_template_xml`.
+-----------------+-------------+-----------------------+---------------+
|cms name |cms type |result name |result type |
+=================+=============+=======================+===============+
|crlIssuingPoint |string |crl_issuing_point |unicode |
+-----------------+-------------+-----------------------+---------------+
|crlUpdate |string |crl_update [1] |unicode |
+-----------------+-------------+-----------------------+---------------+
.. [1] crlUpdate may be one of:
- "Success"
- "Failure"
- "missingParameters"
- "testingNotEnabled"
- "testingInProgress"
- "Scheduled"
- "inProgress"
- "disabled"
- "notInitialized"
'''
request_status = get_request_status_xml(doc)
if request_status != CMS_STATUS_SUCCESS:
response = parse_error_template_xml(doc)
return response
response = {}
response['request_status'] = request_status
crl_issuing_point = doc.xpath('//xml/header/crlIssuingPoint[1]')
if len(crl_issuing_point) == 1:
crl_issuing_point = etree.tostring(
crl_issuing_point[0], method='text',
encoding=unicode).strip()
response['crl_issuing_point'] = crl_issuing_point
crl_update = doc.xpath('//xml/header/crlUpdate[1]')
if len(crl_update) == 1:
crl_update = etree.tostring(crl_update[0], method='text',
encoding=unicode).strip()
response['crl_update'] = crl_update
return response
#-------------------------------------------------------------------------------
from ipalib import Registry, errors, SkipPluginModule
# We only load the dogtag RA plugin if it is necessary to do so.
# This is legacy code from when multiple RA backends were supported.
#
# If the plugins are loaded by the server then load the RA backend.
#
if api.isdone("finalize") and not (
api.env.ra_plugin == 'dogtag' or api.env.context == 'installer'
):
# In this case, abort loading this plugin module...
raise SkipPluginModule(reason='Not loading dogtag RA plugin')
import os
from ipaserver.plugins import rabase
from ipalib.constants import TYPE_ERROR
from ipalib import _
from ipaplatform.paths import paths
register = Registry()
class RestClient(Backend):
"""Simple Dogtag REST client to be subclassed by other backends.
This class is a context manager. Authenticated calls must be
executed in a ``with`` suite::
@register()
class ra_certprofile(RestClient):
path = 'profile'
...
with api.Backend.ra_certprofile as profile_api:
# REST client is now logged in
profile_api.create_profile(...)
"""
DEFAULT_PROFILE = dogtag.DEFAULT_PROFILE
KDC_PROFILE = dogtag.KDC_PROFILE
path = None
@staticmethod
def _parse_dogtag_error(body):
try:
return pki.PKIException.from_json(
json.loads(ipautil.decode_json(body)))
except Exception:
return None
def __init__(self, api):
self.ca_cert = api.env.tls_ca_cert
if api.env.in_tree:
self.client_certfile = os.path.join(
api.env.dot_ipa, 'ra-agent.pem')
self.client_keyfile = os.path.join(
api.env.dot_ipa, 'ra-agent.key')
else:
self.client_certfile = paths.RA_AGENT_PEM
self.client_keyfile = paths.RA_AGENT_KEY
super(RestClient, self).__init__(api)
self._ca_host = None
# session cookie
self.override_port = None
self.cookie = None
@property
def ca_host(self):
"""
:returns: FQDN of a host hopefully providing a CA service
Select our CA host, cache it for the first time.
"""
if self._ca_host is not None:
return self._ca_host
preferred = [api.env.ca_host]
if api.env.host != api.env.ca_host:
preferred.append(api.env.host)
ca_host = find_providing_server(
'CA', conn=self.api.Backend.ldap2, preferred_hosts=preferred,
api=self.api
)
if ca_host is None:
# TODO: need during installation, CA is not yet set as enabled
ca_host = api.env.ca_host
# object is locked, need to use __setattr__()
object.__setattr__(self, '_ca_host', ca_host)
return ca_host
def __enter__(self):
"""Log into the REST API"""
if self.cookie is not None:
return None
# Refresh the ca_host property
object.__setattr__(self, '_ca_host', None)
status, resp_headers, _resp_body = dogtag.https_request(
self.ca_host, self.override_port or self.env.ca_agent_port,
url='/ca/rest/account/login',
cafile=self.ca_cert,
client_certfile=self.client_certfile,
client_keyfile=self.client_keyfile,
method='GET'
)
cookies = ipapython.cookie.Cookie.parse(resp_headers.get('set-cookie', ''))
if status != 200 or len(cookies) == 0:
raise errors.RemoteRetrieveError(reason=_('Failed to authenticate to CA REST API'))
object.__setattr__(self, 'cookie', str(cookies[0]))
return self
def __exit__(self, exc_type, exc_value, traceback):
"""Log out of the REST API"""
dogtag.https_request(
self.ca_host, self.override_port or self.env.ca_agent_port,
url='/ca/rest/account/logout',
cafile=self.ca_cert,
client_certfile=self.client_certfile,
client_keyfile=self.client_keyfile,
method='GET'
)
object.__setattr__(self, 'cookie', None)
def _ssldo(self, method, path, headers=None, body=None, use_session=True):
"""
Perform an HTTPS request.
:param method: HTTP method to use
:param path: Path component. This will *extend* the path defined for
the class (if any).
:param headers: Additional headers to include in the request.
:param body: Request body.
:param use_session: If ``True``, session cookie is added to request
(client must be logged in).
:return: (http_status, http_headers, http_body)
as (integer, dict, str)
:raises: ``RemoteRetrieveError`` if ``use_session`` is not ``False``
and client is not logged in.
"""
headers = headers or {}
if use_session:
if self.cookie is None:
raise errors.RemoteRetrieveError(
reason=_("REST API is not logged in."))
headers['Cookie'] = self.cookie
resource = '/ca/rest'
if self.path is not None:
resource = os.path.join(resource, self.path)
if path is not None:
resource = os.path.join(resource, path)
# perform main request
status, resp_headers, resp_body = dogtag.https_request(
self.ca_host, self.override_port or self.env.ca_agent_port,
url=resource,
cafile=self.ca_cert,
client_certfile=self.client_certfile,
client_keyfile=self.client_keyfile,
method=method, headers=headers, body=body
)
if status < 200 or status >= 300:
explanation = self._parse_dogtag_error(resp_body) or ''
raise errors.HTTPRequestError(
status=status,
reason=_('Non-2xx response from CA REST API: %(status)d. %(explanation)s')
% {'status': status, 'explanation': explanation}
)
return (status, resp_headers, resp_body)
@register()
class ra(rabase.rabase, RestClient):
"""
Request Authority backend plugin.
"""
DEFAULT_PROFILE = dogtag.DEFAULT_PROFILE
def raise_certificate_operation_error(self, func_name, err_msg=None, detail=None):
"""
:param func_name: function name where error occurred
:param err_msg: diagnostic error message, if not supplied it will be
'Unable to communicate with CMS'
:param detail: extra information that will be appended to err_msg
inside a parenthesis
Raise a CertificateOperationError and log the error message.
"""
if err_msg is None:
err_msg = _('Unable to communicate with CMS')
if detail is not None:
err_msg = u'%s (%s)' % (err_msg, detail)
logger.error('%s.%s(): %s', type(self).__name__, func_name, err_msg)
raise errors.CertificateOperationError(error=err_msg)
def _request(self, url, port, **kw):
"""
:param url: The URL to post to.
:param kw: Keyword arguments to encode into POST body.
:return: (http_status, http_headers, http_body)
as (integer, dict, str)
Perform an HTTP request.
"""
return dogtag.http_request(self.ca_host, port, url, **kw)
def _sslget(self, url, port, **kw):
"""
:param url: The URL to post to.
:param kw: Keyword arguments to encode into POST body.
:return: (http_status, http_headers, http_body)
as (integer, dict, str)
Perform an HTTPS request
"""
return dogtag.https_request(
self.ca_host, port, url,
cafile=self.ca_cert,
client_certfile=self.client_certfile,
client_keyfile=self.client_keyfile,
**kw)
def get_parse_result_xml(self, xml_text, parse_func):
'''
:param xml_text: The XML text to parse
:param parse_func: The XML parsing function to apply to the parsed DOM tree.
:return: parsed result dict
Utility routine which parses the input text into an XML DOM tree
and then invokes the parsing function on the DOM tree in order
to get the parsing result as a dict of key/value pairs.
'''
parser = etree.XMLParser()
try:
doc = etree.fromstring(xml_text, parser)
except etree.XMLSyntaxError as e:
self.raise_certificate_operation_error('get_parse_result_xml',
detail=str(e))
result = parse_func(doc)
logger.debug(
"%s() xml_text:\n%r\nparse_result:\n%r",
parse_func.__name__, xml_text, result)
return result
def check_request_status(self, request_id):
"""
:param request_id: request ID
Check status of a certificate signing request.
The command returns a dict with these possible key/value pairs.
Some key/value pairs may be absent.
+-------------------+---------------+---------------+
|result name |result type |comments |
+===================+===============+===============+
|serial_number |unicode [1]_ | |
+-------------------+---------------+---------------+
|request_id |unicode [1]_ | |
+-------------------+---------------+---------------+
|cert_request_status|unicode [2]_ | |
+-------------------+---------------+---------------+
.. [1] The certID and requestId values are returned in
JSON as hex regardless of what the request contains.
They are converted to decimal in the return value.
.. [2] cert_request_status, requestStatus, may be one of:
- "begin"
- "pending"
- "approved"
- "svc_pending"
- "canceled"
- "rejected"
- "complete"
The REST API responds with JSON in the form of:
{
"requestID": "0x3",
"requestType": "enrollment",
"requestStatus": "complete",
"requestURL": "https://ipa.example.test:8443/ca/rest/certrequests/3",
"certId": "0x3",
"certURL": "https://ipa.example.test:8443/ca/rest/certs/3",
"certRequestType": "pkcs10",
"operationResult": "success",
"requestId": "0x3"
}
"""
logger.debug('%s.check_request_status()', type(self).__name__)
# Call CMS
path = 'certrequests/{}'.format(request_id)
try:
http_status, _http_headers, http_body = self._ssldo(
'GET', path, use_session=False,
headers={
'Accept': 'application/json',
},
)
except errors.HTTPRequestError as e:
self.raise_certificate_operation_error(
'check_request_status',
err_msg=e.msg,
detail=e.status # pylint: disable=no-member
)
# Parse and handle errors
if http_status != 200:
# Note: this is a bit of an API change in that the error
# returned contains the hex value of the certificate
# but it's embedded in the 404. I doubt anything relies
# on it.
self.raise_certificate_operation_error('check_request_status',
detail=http_status)
try:
parse_result = json.loads(ipautil.decode_json(http_body))
except ValueError:
logger.debug("Response from CA was not valid JSON: %s", e)
raise errors.RemoteRetrieveError(
reason=_("Response from CA was not valid JSON")
)
operation_result = parse_result['operationResult']
if operation_result != "success":
self.raise_certificate_operation_error(
'check_request_status',
cms_request_status_to_string(operation_result),
parse_result.get('errorMessage'))
# Return command result
cmd_result = {}
if 'certId' in parse_result:
cmd_result['serial_number'] = int(parse_result['certId'], 16)
if 'requestID' in parse_result:
cmd_result['request_id'] = int(parse_result['requestID'], 16)
if 'requestStatus' in parse_result:
cmd_result['cert_request_status'] = parse_result['requestStatus']
return cmd_result
def get_certificate(self, serial_number):
"""
Retrieve an existing certificate.
:param serial_number: Certificate serial number. May be int,
decimal string, or hex string with "0x"
prefix.
The command returns a dict with these possible key/value pairs.
Some key/value pairs may be absent.
+-----------------+---------------+---------------+
|result name |result type |comments |
+=================+===============+===============+
|certificate |unicode [1]_ | |
+-----------------+---------------+---------------+
|serial_number |unicode [2]_ | |
+-----------------+---------------+---------------+
|revocation_reason|int [3]_ | |
+-----------------+---------------+---------------+
.. [1] Base64 encoded
.. [2] Passed through RPC as decimal string. Can convert to
optimal integer type (int or long) via int(serial_number)
.. [3] revocation reason may be one of:
- 0 = UNSPECIFIED
- 1 = KEY_COMPROMISE
- 2 = CA_COMPROMISE
- 3 = AFFILIATION_CHANGED
- 4 = SUPERSEDED
- 5 = CESSATION_OF_OPERATION
- 6 = CERTIFICATE_HOLD
- 8 = REMOVE_FROM_CRL
- 9 = PRIVILEGE_WITHDRAWN
- 10 = AA_COMPROMISE
"""
logger.debug('%s.get_certificate()', type(self).__name__)
# Call CMS
path = 'certs/{}'.format(serial_number)
try:
_http_status, _http_headers, http_body = self._ssldo(
'GET', path, use_session=False,
headers={
'Accept': 'application/json',
},
)
except errors.HTTPRequestError as e:
self.raise_certificate_operation_error(
'get_certificate',
err_msg=e.msg,
detail=e.status # pylint: disable=no-member
)
try:
resp = json.loads(ipautil.decode_json(http_body))
except ValueError:
logger.debug("Response from CA was not valid JSON: %s", e)
raise errors.RemoteRetrieveError(
reason=_("Response from CA was not valid JSON")
)
# Return command result
cmd_result = {}
if 'Encoded' in resp:
s = resp['Encoded']
# The 'cert' plugin expects the result to be base64-encoded
# X.509 DER. We expect the result to be PEM. We have to
# strip the PEM headers and we use PEM_CERT_REGEX to do it.
match = x509.PEM_CERT_REGEX.search(s.encode('utf-8'))
if match:
s = match.group(2).decode('utf-8')
cmd_result['certificate'] = s.strip()
if 'id' in resp:
serial = int(resp['id'], 0)
cmd_result['serial_number'] = unicode(serial)
cmd_result['serial_number_hex'] = u'0x%X' % serial
if 'RevocationReason' in resp and resp['RevocationReason'] is not None:
cmd_result['revocation_reason'] = resp['RevocationReason']
return cmd_result
def request_certificate(
self, csr, profile_id, ca_id, request_type='pkcs10'):
"""
:param csr: The certificate signing request.
:param profile_id: The profile to use for the request.
:param ca_id: The Authority ID to send request to. ``None`` is allowed.
:param request_type: The request type (defaults to ``'pkcs10'``).
Submit certificate signing request.
The command returns a dict with these key/value pairs:
``serial_number``
``unicode``, decimal representation
``serial_number_hex``
``unicode``, hex representation with ``'0x'`` leader
``certificate``
``unicode``, base64-encoded DER
``request_id``
``unicode``, decimal representation
"""
logger.debug('%s.request_certificate()', type(self).__name__)
# Call CMS
template = '''
{{
"ProfileID" : "{profile}",
"Renewal" : false,
"RemoteHost" : "",
"RemoteAddress" : "",
"Input" : [ {{
"id" : "i1",
"ClassID" : "certReqInputImpl",
"Name" : "Certificate Request Input",
"ConfigAttribute" : [ ],
"Attribute" : [ {{
"name" : "cert_request_type",
"Value" : "{req_type}",
"Descriptor" : {{
"Syntax" : "cert_request_type",
"Description" : "Certificate Request Type"
}}
}}, {{
"name" : "cert_request",
"Value" : "{req}",
"Descriptor" : {{
"Syntax" : "cert_request",
"Description" : "Certificate Request"
}}
}} ]
}} ],
"Output" : [ ],