mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 02:55:54 +03:00
[GH-ISSUE #363] [BUG] Fails to authenticate with accentuated char in password #813
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#813
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @loxK on GitHub (Jul 1, 2022).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/363
When the user's password contains an accentuated character (verified with char
ù), it fails to authenticate :@aluxnimm commented on GitHub (Jul 4, 2022):
What network settings to you use in the sync profile advanced settings? Is Force Basic Auth activated, does it make any difference if you turn it off or use preemtive auth?
@loxK commented on GitHub (Jul 4, 2022):
It works with
Force Basic Authactivated.preemtive authdoesn't change anythingSo, there is a workaround (thks), but password without accentuated chars do work with default settings whereas any password should work.
(sorry, forgot to specify that is connecting to Nextcloud 24 from Outlook 2206 on Windows 10)
@aluxnimm commented on GitHub (Jul 4, 2022):
When using force basic auth we manually write the authentication header and use base64 encoded data of the utf8 username and password fields, so that combination seems to work for special chars. Without that option we just use the default settings of the C# HttpClient and NetworkCredential classes, there is no way to change the Encoding there I guess, so I am not sure how to change the behaviour.
@loxK commented on GitHub (Jul 5, 2022):
Are the C# libs closed source ?
@aluxnimm commented on GitHub (Feb 16, 2023):
Will change force basic authentication where we manually add the header in the correct encoding as default for new profiles in the next release to fix those issues.