ASWebAuthenticationSession cookie

Hi All, I am getting stuck while authenticating using ASWebAuthenticationSession. When I am authenticating using a certificate(provided through the MDM profile) the ASWebAuthenticationSession window is stuck with the following image shown in the window. It seems that the ASWeb is not redirecting to customSchemeURL so that we can pick up the authorization code from there. Strangely enough, when we cancel the flow and again retrigger the authentication everything works fine. This scenario happens only once for a fresh installation. Any idea how to resolve the issue?

Dev environment: MacbookPro, Ventura 13.0.1 XCode 14.1 I’m implementing a feature for an existing MacOS application, which will allow users to launch zoom meetings from the application, and am trying to use ASWebAuthenticationSession to implement OAuth2. I’ve confirmed that universal links are correctly configured and working for the app (which is using an https-based redirect URI). In my app delegate, I’ve implemented the following for universal links: - (BOOL)application:(NSApplication *)application continueUserActivity:(NSUserActivity *)userActivity restorationHandler:(void (^)(NSArray> *restorableObjects))restorationHandler { if ([userActivity.activityType isEqualToString: NSUserActivityTypeBrowsingWeb]) { NSURL *url = userActivity.webpageURL; if ([url.path containsString:[NSString stringWithStdString:Zoom::kFragment]]) { std::string urlStr((url.absoluteString).stdString); //DBG DialogFactory::GetInstance()->Message(Universal links handler - AppDelegate: Handling response: + urlStr); //DBG

Environment details: MacbookPro, Ventura 13.0.1 XCode 14.1 I’m trying to use ASWebAuthenticationSession to implement OAuth2 for a MacOS application. When Chrome is my default browser, starting a session crashes the application. When either Firefox or Safari are the default browser, starting a session launches Safari with the login page. After logging in, instead of redirecting back to the application and invoking my session handler, a 404 page is displayed. Also displayed is a banner near the top of the window, containing an open button and instructions: “Open in the MyApp app”. Clicking the button redirects back to the app, and the OAuth received by the application:continueUserActivity:restorationHandler: method that I implemented in NSAppDelegate for Universal links. My session handler never receives the OAuth response or an error. Is there a solution or workaround for this? Thanks for any help.

We’re using ASWebAuthenticationSession with Universal Link for the redirectURI. On success sign-in, server returns an universal link with the authentication code. The SceneDelegate, func scene( scene: UIScene, continue userActivity:) is called, but the completionHandler from the WebAuthentication Session is never called and the sign-in screen never dismiss. Do you have an idea why? Do you have a sample Xcode project?

ASWebAuthenticationSession works wrong when called second time in a row. So our web authentication code is organised like this: if let existingSession = ssoAuthSession { // closes the auth window but then request queue gets stuck: existingSession.cancel() } let session = ASWebAuthenticationSession(url: signinURL, callbackURLScheme: callbackScheme) { (receivedURL, error) in /// handle the result, DispatchQueue.main.async { // report the result self.ssoAuthSession = nil } } session.prefersEphemeralWebBrowserSession = true session.presentationContextProvider = delegate //delegate provides a valid app window if !session.canStart() { // report error, (doesn't happen) return } self.ssoAuthSession = session self.ssoAuthSession.start() The problem is, if the user initiates the SSO Authentication second time without closing the previous browser authentication window, that old window closes (as we cancelled the old session), but the new window never opens. This reproduces 100% on every default browser

Our company is rolling out the 'Sign in with Apple' feature, when deployed to our alpha env, we met a block issue: when Apple redirect back to our service, sometimes it will miss all cookies, which one is used to mark which server the original request from, Our alpha env have more than one server.There's some probability that this behavior will happen. Any of you have this situation?

Hi everyone, I am trying to authenticate an user through ASWebAuthenticationSession, and after that redirect to an URL that uses the callback scheme. The authentication page URL is correctly loaded on a browser thanks to ASWebAuthenticationPresentationContextProviding. But after form completed and authentication successfully, what I am doing is a redirect directly from my server to http://localhost:5000/ios/hola?hola=hola I am trying to catch this URL using a callbackScheme in my iOS app, using the same url that the one which I redirected the browser to, but this is not working. I also tried to create a Scheme URL to my identifier, and pass it to the callbackScheme, but this is not working either. Documentation is not very clear at how to manage the authentication callback and as a beginner I don't know the way to solve this. Some help would be appreciated. Thank you for your time! PD: This is the code of my class @available(iOS 12.0, *) class AuthView: UIViewController { var authSession: ASWebAuthenticationSession

I need a way to accept third party cookies in WKWebViews. It seems the latest iOS is blocking my site from fully loading due to third party cookies.