Achaz / Achaz/imsdroid

Use stack.putDocument in XCAP received 401 Unauthorized

Open
#521 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
Java
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
What steps will reproduce the problem?
1. Use putDocument() in XCAP stack
2. Server reponsed 401 Unauthorized which client not put again in
Proxy-authorization: nonce="xxx" reponse="xxx"
3. SIP request was OK, first also received 401 Unauthorized then in second
request, it send nonce, username, reponse to authenticate.
4. Doubango 2.0 not allow xcap message?

What is the expected output? What do you see instead?
A should be able to reponse 200 OK in second request.

What version of the product are you using? On what operating system?
Android 4.2.2

Please provide any additional information below.
IMSdroid 2.569.1089
```

Original issue reported on code.google.com by `mr.kun...@gmail.com` on 13 Jun 2014 at 2:13

Attachments:
- [put_xcap.txt](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-521/comment-0/put_xcap.txt)
- [respone_xcap.txt](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-521/comment-0/respone_xcap.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the attached put_xcap.txt and respone_xcap.txt traces, then trace the XCAP putDocument() request in IMSdroid on Android. Compare the first and second 401 Unauthorized responses with the SIP authentication flow; done means the second request includes the required nonce, username, and response and receives 200 OK.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authentication, mobile-dev, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.