ASWebAuthenticationSession cookie

Did you mean 'apple pay?What version Safari on what macOS?Did you clear Safari cache/cookies?

Did you test on 10.11 or 10.12?I just tried on 10.12 (macOS Sierra), and storage.cookies returned zero cookies, where _storage_ was initialized with the @Cookies group identifier.

Hello, I fixed this problem.At first I use Google Chrome browser to register, purchase and get an activation code, however the activation process gets unknown error and cannot complete.I switch to Safari browser, login and activate succesfully. Maybe there is a problem with website's cookies.

To start, error 401 means “Unauthorized”, meaning that the request failed but could succeed if you authenticated properly.Web sites usually authenticate requests in one of three ways:CookiesHTTP authentication (Basic, Digest, and so on)Some custom scheme, like a custom HTTP headerThe first approach is by far the most common, but you’ll have to confirm which approach is in play before moving on. There may be helpful hints in the 401 response itself (for example, a WWW-Authenticate header), or you may need to look at how the web browser is doing its authentication. If, as I suspect, the site is using cookies, you’ll have to copy the cookies from the web view to your native request. This can be a bit tricky. There is, alas, no way to set up an WKWebView to share its cookie context with an NSURLSession (although that would make a fine enhancement request; if you do file such a request, please post your bug number, just for the record). In most cases you can get the required cookies

It would require at least one sign in, with the option to stay that way, typically via a cookie, but I'd not depend on it working every time 😉

You’ll need to provide more specific details if you want a detailed answer. Reading your question I’m not even sure if you’re asking about how to do this on the server side or on the client side? If it’s on the client side, the answer depends on how the server side works. Does it, say, using cookies for authentication? Or HTTP authentication? Or OAuth? Different web servers work in different ways, making a general answer impossible.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Whilst looking into cookies I found something very odd. To get a cookie for stay signed in I used Youtube as a test and after signing in tried a google search and came to the same problem, google search links don't do anything. However after signing out from youtube it works again.Is there somewhere I can put this for attention / bug report ?

Going with KMT on this one, just the usual stay signed in option, didn't realise it's set by a cookie.

I dug into this issue as part of a DTS incident (s. 656775591) and my final conclusion was:There’s no direct answer to this problem, so the other developer ended up filing an enhancement request about this (r. 29992970). Feel free to file your own bug report describing your own specific requirements here.The NSURLErrorClientCertificateRequired error you see in this case is triggered by a specific sequence of events: If the request fails with 403And the delegate responded to the client identity authentication challengeAnd the app has multiple digital identities in its keychain (this criteria is only applied on macOS; on iOS-based platforms it’s assumed to be true)Fail the request with NSURLErrorClientCertificateRequiredOtherwise, deliver the 403 responseIf you have any control over the server then a good way to approach this issue is to have it set the certificate_authorities field in the CertificateRequest message (see Section 7.4.4 of RFC 5246). You can get this from the client identity authentication challe

I am already on the latest versions. I have tried revoking the old certificate, created a new one, installed and restarted MBP but safari extensions builder still says No safari extensions certificate. I have also tried clearing the cookies and cache in vein.

Using Safari/macOS as an example, try clearing cookies/caches, then go again.