| 3 | | I am running the xpra proxy server as an Kubernetes ingress server. Therefor I merged the pam_auth.py and exec_auth.py to a new module pamexec_auth.py and placed it in the Xpra tree. The following is done by this module first a normal validation with PAM and when this is a succesfull login it starts a script to create or re-connect a running Xpra pod with a predefined session. The script must return a string with the following form "testuser2|NA|545400003|545400003|tcp:192.168.81.136:14500|||" like the SQlite module. The script needs some information from the client side. (argv) In de server_core module there is a def process_hello (XXXX) place before the line 'capabilities = packet[1]' the line 'global capabilities'. The module pamexec is then able to import capabilities and update the display with tcp:<ip-addres>. |
| 4 | | In the upcoming days when I have some time I will upload scripts etc. to https://github.com/louis-mulder/Xpra-VDI-Netes |
| | 3 | I am running the xpra proxy server as an Kubernetes ingress server. Therefor I merged the `pam_auth.py` and `exec_auth.py` to a new module `pamexec_auth.py` and placed it in the Xpra tree. The following is done by this module first a normal validation with PAM and when this is a successful login it starts a script to create or re-connect a running Xpra pod with a predefined session. The script must return a string with the following form |
| | 4 | {{{ |
| | 5 | testuser2|NA|545400003|545400003|tcp:192.168.81.136:14500||| |
| | 6 | }}} |
| | 7 | like the SQlite module. The script needs some information from the client side. (argv) In the `server_core` module there is a `def process_hello (XXXX)` place before the line `capabilities = packet[1]` the line `global capabilities`. The module `pamexec` is then able to import capabilities and update the display with `tcp:<ip-addres>`. |
| | 8 | In the upcoming days when I have some time I will upload scripts etc. to [https://github.com/louis-mulder/Xpra-VDI-Netes] |
copyleft 2010 - 2021
