nextcloud / nextcloud/user_saml
Update of User_saml app breaks user_saml
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Hello i installed NC 19 with user_saml and ldap backend, everything working fine, (was using duo access gateway for SAML)
I just updated NC 19 -> NC20 and Saml authentication is not working anymore.
I can use direct login, so that part works fine.
- OS Ubuntu 18.04
- mariadb
- nginx
- php 7.4
When i try logging in using SAML i get Account not provisioned.
in the logs:
[user_saml] Fatal: No InResponseTo at the Response, but it was provided the requestId related to the AuthNRequest sent by the SP: ONELOGIN_e40f79f35f16d5ce674e5342399c0bf0..
POST /apps/user_saml/saml/acs
from <ip> at 2020-11-03T15:36:53+01:00
and:
[user_saml] Fatal: invalid_response
POST /apps/user_saml/saml/acs
from <ip> at 2020-11-03T15:36:53+01:00
I tried a fresh install on a new machine, same issue
any ideas?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the /apps/user_saml/saml/acs endpoint and review the logged invalid_response and “No InResponseTo” failures after upgrading Nextcloud 19 to 20. Reproduce the SAML login failure in the listed environment; done means SAML login works without “Account not provisioned” while direct login remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100