nextcloud / nextcloud/user_saml
"User is not Provisioned" is error message for anything that goes wrong.
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
The error message "User is not Provisioned" is ussed for anything that goes during the saml login.
Can be that:
- messages from the server are not correctly signed (at least that appears in the log)
- the ldap mapper messed up the user mapping,
- Can be that the user does not exist in the ldap plugin (it is filtered out because it doesn't belong to the right group)
- I remember I saw it on other occasions, but don't remember which ones.
It would be great if there would be more specific error message to the user. Would make debugging a lot easier.
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
Search the SAML login flow for every path producing "User is not Provisioned", then compare the server-signature, LDAP mapping, and LDAP group-filtering cases described in the issue. Done means users receive distinct, actionable messages for the different failure causes and the existing login behavior remains covered by the project's tests.
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