-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basic auth request (401) when _CONF_CHECK_ISSUE_UPDATE_CONFLICT is true #104
Comments
I have the same experience. When I open issue detail page, after few seconds http authentication window pops up.
Environment: |
Same problem here on Redmine 4.2.8 on Ruby 2.7.6 with other plugins additionals 3.0.5.2 and additional_tags 1.0.4. |
same problem here on Redmine 4.2.8 on Ruby 2.7.2 |
Hi, Hope it will be fixed soon :) thx |
I have the same problem. It looks like the javascript has been changed to request /issues/51762.json instead of /issues/51762. The change triggers basic auth. The workaround in my case is that I use an older version. The git version that works for me is 750e602. |
Code is here and PR are open Thank you @iprok and @pbolle for the complete and useful answer |
To much credit ^^ I would gladly if I known how to. In the mean time I disabled the conflict check, and it's working. No more auth popup. I'll patiently wait for you or the community to fix then :) |
Has the issue been resolved? When can we expect the fixed version to be released? |
Ok, fix deployed on my redmine and looks functional to me. Well done @k41n , thanks a lot :) |
Can we get a fixed version for this issue? My org will not allow the use of patches/unofficial versions, and this is causing issues since we are also under pressure to disable basic auth. |
Last commit f4f2862 may resolve the issue by disabling JSON Redmine API call |
Hello!
I just updated redmine 4.1 to 5.0 with latest version of your plugin.
Redmine version: 5.0.4.stable
redmine_issue_dynamic_edit 0.9.1 (just cloned from master)
When any issue page is opened I'm getting basic authentication request. The user is already authorized in redmine. I think it's because links like myredmine/issues/9219.json requires the user to be authorized with "basic" http-authorization. If I enter my redmine login and password in this basic auth window, it works as usual.
The request that leads to 401 (I cut away some private info):
The request that is answered with 200:
The text was updated successfully, but these errors were encountered: