contextualise-ssh-server
Contextualise motley-cue and pam-ssh-oidc on a VM Server
Installation
contextualise-ssh-server is available on PyPI. Install using pip:
pip install contextualise_ssh_server
Configuration
Config is read from /etc/contextualise_ssh_server.conf
There is a default config file in the place where pip installs this package
There you will also find templates for motley_cue.conf and feudal_adapter.conf
Environment Variables
These control the behaviour:
-
SSH_AUTHORISE_OTHERS_IN_MY_VO: If set to a nonempty value ALL members of ALL VOs of the user will be authorised to log in. -
SSH_AUTHORISE_VOS: If the above variable is not set and this variable specifies a json list of VOs (actually AARC-G069/G027 Entitlements) to authorise.Example:
export SSH_AUTHORISE_VOS="['urn:mace:egi.eu:group:cryoem.instruct-eric.eu:admins:role=owner#aai.egi.eu', 'urn:mace:egi.eu:group:umsa.cerit-sc.cz:admins:role=owner#aai.egi.eu']
Usage
The tools will output the two config files motley_cue.conf and
feudal_adapter.conf in the folder in which it is called.
Those need to be placed in /etc/motley_cue with the access token of the
user as the only parameter:
contextualise_ssh_server <OIDC_ACCESS_TOKEN>
PAM
For enabling and disabling tokens in pam, you can use the scripts
enable-pam-ssh.sh and disable-pam-ssh.sh
They are installed into the same folder as the python file, which you can
find with contextualise_ssh_server -b
VM Integration
Install packages to VM image:
yum install motley-cue pam-ssh-oidc
Include this in the VM startup:
# enable tokens in pam:
`contextualise_ssh_server -b`/enable-pam-ssh.sh
# create motley-cue config
cd /tmp
contextualise_ssh_server $USER_OIDC_ACCESS_TOKEN
# place them in /etc/motley_cue/
sudo cat motley_cue.conf > /etc/motley_cue/motley_cue.conf
sudo cat feudal_adapter.conf > /etc/motley_cue/feudal_adapter.conf
Metadata
Release files for contextualise-ssh-server 0.8.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| contextualise_ssh_server-0.8.6.tar.gz | 21.0 kB | Without provenance | Details for contextualise_ssh_server-0.8.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| contextualise_ssh_server-0.8.6-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for contextualise_ssh_server-0.8.6-py2.py3-none-any.whl |
Total release size: 42.5 kB
Release files / contextualise_ssh_server-0.8.6.tar.gz
| Download URL | contextualise_ssh_server-0.8.6.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d50f122bcb97b381cd76d810d50a74530452630a05fa14661424b65068d55981
|
|
BLAKE2b-256 checksum How to use checksums |
595f2ff37d086146a9d0d84649c7b9a578a9cf4a96c42a0e18226c4ec4c05169
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / contextualise_ssh_server-0.8.6-py2.py3-none-any.whl
| Download URL | contextualise_ssh_server-0.8.6-py2.py3-none-any.whl |
|---|---|
| Size | 21.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f5c2e09ca362d3b74b23590a11aec9cd7b40ac0445d465bb0813ddc951a5a678
|
|
BLAKE2b-256 checksum How to use checksums |
0b9a1ae279392d63057c1e3569beffb660f17589d20c3b5ad0891f5156753152
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for contextualise-ssh-server 0.8.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.