summaryrefslogtreecommitdiff
path: root/src/saml2/entity.py
diff options
context:
space:
mode:
authorClint Byrum <clint@fewbar.com>2015-05-27 10:05:48 -0700
committerClint Byrum <clint@fewbar.com>2015-05-28 09:50:57 -0700
commit695e7b0c96c8965e357d8389d3b3be087928f0e3 (patch)
tree767d8a5f9ea4bd8eb35bb3f53c215cd345ebbb03 /src/saml2/entity.py
parent7c84f6f28637a39cc0a7d42a89f348759a0d0235 (diff)
downloadpysaml2-695e7b0c96c8965e357d8389d3b3be087928f0e3.tar.gz
Deal with stricter bytes/strings in py3
Several more instances of test failures in python3 caused by incompatible use of bytes vs. strings. Notable difference from other similar patches is that ascii can be used for encoding certificate strings since they are base64 encoded.
Diffstat (limited to 'src/saml2/entity.py')
-rw-r--r--src/saml2/entity.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/saml2/entity.py b/src/saml2/entity.py
index 754d2f03..6d868b5b 100644
--- a/src/saml2/entity.py
+++ b/src/saml2/entity.py
@@ -540,7 +540,7 @@ class Entity(HTTPBase):
_cert = "%s%s" % (begin_cert, _cert)
if end_cert not in _cert:
_cert = "%s%s" % (_cert, end_cert)
- _, cert_file = make_temp(_cert, decode=False)
+ _, cert_file = make_temp(_cert.encode('ascii'), decode=False)
response = cbxs.encrypt_assertion(response, cert_file,
pre_encryption_part(), node_xpath=node_xpath)
return response