Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add a mention of django-filesify for managing cert and key #389

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add a mention of django-filesify for managing cert and key #389

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/source/contents/setup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -665,6 +665,8 @@ SAML2 certificate creation example::
PySAML2 certificates are files, in the form of strings that contains a filesystem path.
What about configuring the certificates in a different way, in case we are using a container based deploy?

- You could try using a third-party package like `django-filesify <https://pypi.org/project/django-filesify/>`_ to create a physical files from a secured database text field where the cert and key are stored.

- You could supply the cert & key as environment variables (base64 encoded) then create the files when the container starts, either in an entry point shell script or in your settings.py file.

- Using `Python Tempfile <https://docs.python.org/3/library/tempfile.html>`_ In the settings create two temp files, then write the content configured in environment variables in them, then use tmpfile.name as key/cert values in pysaml2 configuration.