#3763: GET /horse/_changes?feed=websocket

23:38:29.922535 HTTP: #3763:     --> 401 Login required  (0.0 ms

No clue what's "going wrong" cause we have no idea what the process should 
be..

1. POST request to /$DB/_user/. -> Successfull, we have a sync user now.

2. NSURLCredential *cred = [NSURLCredential

                             credentialWithUser: xxxx

                             password:xxxx

                             persistence: 
NSURLCredentialPersistencePermanent];

    NSLog(@"cred = %@", cred);

NSURLProtectionSpace* space;

    space = [[NSURLProtectionSpace alloc]

             initWithHost: @"http://xxxx";

             port: xxxx

             protocol: @"https"

             realm: @"xxxx"

             authenticationMethod: NSURLAuthenticationMethodDefault];

    NSLog(@"space = %@", space); 

    [[NSURLCredentialStorage sharedCredentialStorage] setDefaultCredential: 
nil forProtectionSpace: space];

- The realm is correct yes.

3. Create session for user trough Custom (Indirect) Authentication protocol.

 The session "documents" looks correct and the response is successfull.


//CouchbaseLover



Den fredagen den 13:e juni 2014 kl. 21:16:08 UTC+2 skrev Jens Alfke:
>
>
> On Jun 13, 2014, at 10:35 AM, CouchbaseLover <[email protected] 
> <javascript:>> wrote:
>
> 1.  Why is it working differently if you set it to continuous false/true 
> when it comes to User Management ? 
>
>
> I don’t know. The main difference is the way the _changes feed gets 
> requested, so there may be some issue with auth there.
>
> Can you describe what exactly is going wrong in your app when you use 
> continuous replication?
>
> —Jens
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/c8ff9ab5-9939-40bf-9318-59e2ccd3e181%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to