ASWebAuthenticationSession cookie

Hello, I'm implementing ASWebAuthenticationSession to make a sign in. ASWebAuthenticationSession it uses SFSafariViewController to display the sign in URL, but after make the sign in, there is no prompt to ask to the user to store their credentials. Using directly SFSafariViewController this prompt appears. Even the suggestion to change the password to one stronger. Is this issue happening to someone else? Thank you very much

Hi, Does anyone knows, if I can redirect a user to the broswer, to open authentication pages (ike Google, Facebook or other agents) instead of use the SDK and in-app browsers (like WKWebView/SFSafari)? I need to open a URL provided by backend services, but in ASWebAuthenticationSession I cant use the callbackScheme in the URL, it doesn't allow / and : symbols to close the moda. So, if I can, will my app be accepted by apple to publish on App Store? Or if I can't, how should I fix that problem? Thank you for your help.

Hi, I want use ASWebAuthenticationSession to autofill login/password on a website. I tried some code but it doesn't work it always prompt me for password. First I goto webSITE from button click action and then get the permissions prompt;https://pasteboard.co/IvzRXGZ.pngThen, after clicking continue button, the website prompts me for password;https://pasteboard.co/IvzSJjs.pngI fill in my username and password.Now, next time I go to page it SHOULD autofill with the login and password I entered. Its asking for login and password instead!Here is code excerpt;#import ViewController.h #import <AuthenticationServices/AuthenticationServices.h> @interface ViewController () @property (strong) ASWebAuthenticationSession *session; @end @implementation ViewController @synthesize session; - (void)viewDidLoad { [super viewDidLoad]; } - (IBAction)loginBtnClicked:(id)sender { NSURL *destinationUrl = [NSURL URLWithString:@https://site.name.edu]; NSString *callbackUrlScheme = @https://site.name.edu/Pages

Can we disable ITP for Safari web extension pages (including the new tab page)? Extension pages are trusted views as the user has installed the extension and granted permissions. ITP adding storage and cookie isolation here affects functionality for any embedded frames in extension pages. StorageAccess API i also not useful here since the GUID of the parent extension page will change every time the browser launches, nullifying the granted access.

We're using ASWebAuthenticationSession to kickstart the auth flow in our Mac app. Most of the time when we start the auth session, Chrome is launched and authentication flow proceeds as expected (because Chrome is the default browser). On the same machine with same configuration, some times Safari is launched. What might be wrong ?

Hi! I'm facing the following issue in different versions of Safari: When removing cookies via PHP on log out of an application I can see that the Safari Developer Tools > Storage > Cookies (of the website) removes the cookies from the list. So my user cookie is no longer there as expected, all good. However, if I run document.cookie on the console or document.cookie.includes('user') I can see the cookie listed there. I would expect the document.cookie to be updated with the Storage tab as it happens on the other browsers. Does anyone know why is this happening? Is there anything special that must be done for Safari to remove the cookie from there? This behaviour is consistent in versions v14, v15 and v16 of Safari. Thank you for your time. Regards, Borja.

PWA Freezing after OpenID authorizes user [iOS Safari Standalone] I have built a simple PWA for our security staff that allows employees to click links and view content about our company's policies on various matters. The app uses Microsoft's OWIN middleware library to authorize our employees' access into the app via their enterprise Microsoft login creds. When a user clicks the 'Employee Sign in' prompt on our login page, they are redirected to Microsoft's domain to complete the sign-in process. Once sign in is complete, they are redirected back to our app's home page. The Problem The problem appears only to arise when iOS users (v13) pin the app to their homescreen and then launch the app in standalone mode, and only after the user has completely terminated the app and then returned. We've tested the app on Chrome, Safari (non-standalone mode), Firefox, and the issue does not present in those browswers. The app functions seamlessly up until the point that the user has completed their Microsoft signin and be