nextcloud / nextcloud/user_saml
Meta data fetched from wrong (first) configuration when a different one is active
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Steps to reproduce
- Create a second configuration
- See "metadata valid" success message
- wonder why auth is not working as expected
Expected behaviour
Meta data of the current config is fetched
Actual behaviour
Config parameter is not send to the server, so meta data of the "1" config is fetched
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
No file or test is named in the issue. Reproduce the problem with a second configuration, then trace the request that fetches metadata and verify how the active configuration is passed to the server. Done means metadata is fetched for the current configuration and authentication works with that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100