Search results for

ASWebAuthenticationSession cookie

1,295 results found

Post

Replies

Boosts

Views

Activity

NSURLConnection finished with error - code -1100
I am running application in XCode 14.3.1 which build using Visual Studio 2017 (Apache Cordova) and getting below error. 2023-09-04 13:38:59.119104+0530 CC Mobile[7551:1246047] ADAL version 2.3.1 2023-09-04 13:38:59.315325+0530 CC Mobile[7551:1246047] DiskCookieStorage changing policy from 2 to 0, cookie file: file:///Users/sankum03/Library/Developer/CoreSimulator/Devices/ECFE254E-3529-4220-AE0D-10C143E96610/data/Containers/Data/Application/D2125721-3B33-442F-994A-B606C5D6B61C/Library/Cookies/com.protiviti.CC.mobile.0001.binarycookies 2023-09-04 13:38:59.364681+0530 CC Mobile[7551:1246047] Apache Cordova native platform version 4.3.0 is starting. 2023-09-04 13:38:59.364914+0530 CC Mobile[7551:1246047] Multi-tasking -> Device: YES, App: YES 2023-09-04 13:38:59.784539+0530 CC Mobile[7551:1246047] Using UIWebView 2023-09-04 13:38:59.788448+0530 CC Mobile[7551:1246047] [CDVTimer][handleopenurl] 0.221014ms 2023-09-04 13:38:59.792992+0530 CC Mobile[7551:1246047] [CDVTimer][intentandnavigationfil
1
0
733
Sep ’23
Clearing cookies in SFSafariViewController?
I am using SFSafariViewController to authenticate against a website (SAML idP) and retaining my session using a cookie. I opted to use SFSafariViewController because my users could log in to the site using Safari or another app's instance of SFVC to achieve single sign on because as I understand it, the cookie store between native Safari and instances of SFSafariViewController are more or less shared. However, clearing the cookies in Safari settings in the settings app doesn't clear the cookies in my app's instance of SFVC. I have also tried logging out of the site in Safari but the cookie / session is still retained in my app's instance of SFVC.Is this expected behavior from SFVC?Thanks,Lucas
Topic: UI Frameworks SubTopic: UIKit Tags:
5
0
11k
Sep ’23
Reply to ASWebAuthenticationSession preferEphemeral = false shows null sign-in dialog
It's difficult to diagnose this without more information. Can you file this through Feedback Assistant, and make sure to include: The system logs gathered by Feedback Assistant (ideally triggered shortly after reproducing the issue). The macOS version you're seeing this on. If it's a beta, does this happen on the current shipping macOS? Is this an existing app that started getting different behavior, or a new app that you haven't seen work before? The arguments you're passing to ASWebAuthenticationSession. Thanks! 🙂
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’23
Reply to WKWebView password autofill
Password AutoFill is the most frustrating concept/feature I have been working on in my many years as an app developer. It's a black box full of magic (or heuristics as Apple calls it) and the documentation is theoretical. ASWebAuthenticationSession didn't help, so my workaround (hack) is to intercept credentials in webView(_:decidePolicyFor:decisionHandler:) on WKNavigationType.formSubmitted navigation type. I put the username and password in native UITextFields that is hidden. Sidenote: This is against all security best practices. The textContentType needs to be set accordingly and the order the UITextFields are added to the parent view is super important, constraints does not seem to matter. Currently this works great on local debug builds, but for some reason doesn't on in-house/enterprise builds. The device console does not show anything helpful other that the com.apple.developer.associated-domains -> webcredentials for the domain was approved. Testing against a local webserver also does not w
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’23
Reply to TestFlight Unavailable
Anyone figure this out, I get a similar error: @Apple as well @leeron Aug 10 19:16:18 TestFlight(libusrtcp.dylib)[13660] : tcp_output [C17.1.1:4] flags=[R.] seq=1279848721, ack=2995965602, win=2047 state=CLOSED rcv_nxt=2995965602, snd_una=1279848697 Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : RP(0x2805420c0) URL=https://testflight.apple.com/v2/accounts/8f5d9d76-6e3e-411a-84b9-6fb853821157/apps/6458789872/builds/120309384/install; code=404; Headers={ Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Connection = close; Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Content-Length = 134; Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Content-Type = application/json; Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Date = Thu, 10 Aug 2023 19:16:18 GMT; Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Server = daiquiri/3.0.0; Aug 10 19:16:18 TestFlight(TestFlightServices)[13660] : Set-Cookie = dc=pv;Version=1;Domain=.itunes.apple.com;Path=/;Max-Age=86400;
Aug ’23
What alternative methods are there for implementing FIDO-based biometric authentication in iOS than passkeys?
Hi, I want to implement FIDO based biometric authentication in our app. I don't want to use passkeys because they are only compatible with iOS 16 and higher. Is there a way to use it through the SFSafariViewController, a web view, ASWebAuthenticationSession or any another method?
3
0
3.4k
Aug ’23
NWConnection WebSocket Protocol hangs on preparing for iOS 13 only
I have a critical issue where my websocket will not connect to a server that is sitting behind an NGINX reverse proxy only on iOS 13. I have tested on both a real device and simulator with no success. It simply hangs on preparing. it never receives updates to the viabilityUpdateHandler and only ever enters the preparing state of the stateUpdateHandler. On any iOS greater or equal to iOS 14 it works seamlessly. I can connect to a local server that is not dealing with any certificates on iOS 13 no problem, but when my production server is in play it does not communicate something properly. I am using NWConnection's NWProtocolWebSocket. The setup is basic and straight forward let options = NWProtocolWebSocket.Options() options.autoReplyPing = configuration.autoReplyPing options.maximumMessageSize = configuration.maximumMessageSize if configuration.urlRequest != nil { options.setAdditionalHeaders(configuration.urlRequest?.allHTTPHeaderFields?.map { ($0.key, $0.value) } ?? []) _ = configuration.cookies.map { cookie
3
0
888
Aug ’23
Error while installing Game Porting Toolkit on the gptk command
Error: Failure while executing; /usr/bin/env /usr/local/Homebrew/Library/Homebrew/shims/shared/curl --disable --cookie /dev/null --globoff --show-error --user-agent Homebrew/4.1.3 (Macintosh; Intel Mac OS X 14.0) curl/8.1.2 --header Accept-Language: en --retry 3 --fail --location --silent --head https://mirrors.ustc.edu.cn/homebrew-bottles/bison-3.8.2.ventura.bottle.tar.gz exited with 35.
1
0
1.1k
Aug ’23
Reply to macOS FIDO2/Webauthn support for web authentication
I also noticed that custom URL scheme and ASWebAuthenticationSession combo doesn't have this Open button issue, but was worried that this is some kind of omission/bug and it may get fixed later. After your explanation it looks like expected behavior and this helps a lot. Essentially applinks purpose is for direct app/browser integration and not meant to work with ASWebAuthenticationSession API. Thank you!
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’23
macOS FIDO2/Webauthn support for web authentication
Hello. Does WKWebView on Mac support FIDO2(webauthn)? We need to implement this in our app and ASWebAuthenticationSession API comes up in searches all the time as the only solution. Is this still the case? From my experiments ASWebAuthenticationSession on Mac doesn't provide best user experience - too much fiddling and odd behavior for an end user. F.e. user needs to click Open button from the browser window to pass token to the very same app which initiated the window and this is not very logical considering all the efforts to setup applink. Would appreciate an advice.
2
0
3.1k
Jul ’23
Reply to macOS FIDO2/Webauthn support for web authentication
Yes, WKWebView supports WebAuthn as long as your app is using Associated Domains (specifically the webcredentials association) with the RPID that you're using. If you need to authenticate to third party services, ASWebAuthenticationSession is the correct solution. For the Open button behavior you're describing, it sounds like you may be either using a Universal Link for your callback rather than a custom URL scheme or your custom URL scheme isn't matching. Using a custom URL scheme is the preferred callback method for ASWebAuthenticationSession and will provide the best user experience (e.g. no Open button). For other platforms, custom URL schemes are generally discouraged because other apps may try to claim the same URL scheme and intercept the response. However, ASWebAuthenticationSession was specifically built to solve that problem and guarantees only the calling app will receive the response (documented here).
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’23