Pydio Issue when accessing through Single Sign On


#1

Over the past weekend, a random issue started with Pydio where when some users access Pydio through our Single Sign-On (Shibboleth) they receive a generic error of:

No active repository found for user!

I then checked our logs and it wasn’t very informative (we are running Pydio off a docker setup, nonetheless this was what was found from the logs:

/usr/lib/python2.6/site-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2019-01-02 18:17:26,198 CRIT Supervisor running as root (no user in config file)
2019-01-02 18:17:26,254 INFO RPC interface 'supervisor' initialized
2019-01-02 18:17:26,254 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2019-01-02 18:17:26,254 INFO supervisord started with pid 1
2019-01-02 18:17:27,271 INFO spawned: 'httpd' with pid 10
2019-01-02 18:17:27,273 INFO spawnerr: can't find command '/usr/sbin/sshd'
2019-01-02 18:17:27,275 INFO spawned: 'generateCert' with pid 11
2019-01-02 18:17:27,279 INFO spawned: 'mysql' with pid 12
2019-01-02 18:17:28,050 INFO exited: generateCert (exit status 0; not expected)
2019-01-02 18:17:29,052 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-02 18:17:29,053 INFO spawnerr: can't find command '/usr/sbin/sshd'
2019-01-02 18:17:29,055 INFO spawned: 'generateCert' with pid 157
2019-01-02 18:17:29,056 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-02 18:17:29,067 INFO exited: generateCert (exit status 0; not expected)
2019-01-02 18:17:31,070 INFO spawnerr: can't find command '/usr/sbin/sshd'
2019-01-02 18:17:31,073 INFO spawned: 'generateCert' with pid 158
2019-01-02 18:17:31,087 INFO exited: generateCert (exit status 0; not expected)
2019-01-02 18:17:34,090 INFO spawnerr: can't find command '/usr/sbin/sshd'
2019-01-02 18:17:34,090 INFO gave up: sshd entered FATAL state, too many start retries too quickly
2019-01-02 18:17:34,092 INFO spawned: 'generateCert' with pid 159
2019-01-02 18:17:34,104 INFO exited: generateCert (exit status 0; not expected)
2019-01-02 18:17:35,108 INFO gave up: generateCert entered FATAL state, too many start retries too quickly

This is what our docker-compose.yml file looks like:

version: "2"
services:
  pydio:
    image: pydio/pydio-core
    ports:
      - "8654:443"
    environment:
      - "VIRTUAL_HOST=our.organization.url:443"
    volumes:
      - ./mysql:/var/lib/mysql:rw
      - ./plugins:/var/lib/pydio/plugins:rw
      - ./personal:/var/lib/pydio/personal:rw

I am honestly not sure where to start as I am a bit unfamiliar with Pydio and would appreciate some pointers to getting this problem resolved so our users can access their files once again.

Happy New Years!


#2

Hi,
could you tell me your authentication setup,
what type of instance is your master and secondary.

i see mutiple instance of this line asking you for the openssh package, how does your single sign on solution work ? (does it require ssh access ?).


#3

Hello,

We are using a regular Shibboleth + CAS setup that connects with our LDAP. Our single sign-on doesn’t require any SSH access but instead usually requires a form of metadata to allow authentication to our services, or in this case, it sits behind our servers so when prompted through our SSO, it would authenticate the user with the appropriate credentials to allow them to see the appropriate files they should be seeing.


#4

Hello, just wanted to follow up and see if there were any ideas on what can be causing these issues?


#5

Hello,

What is version of Pydio?
HOw do you “link” CAS with Pydio? via authfront.cas plugin ?