Oclair wrote:
Barney-15E wrote:
How is the OS is intercepting the content of a 3rd party web browser?
I have no idea what that question has to do with my statement & question.
The image you posted shows that you created a Passkey and asked how you wanted to manage them. Passkeys are not “3rd party web browser” items. If you didn’t want macOS to manage your Passkeys, you should not have chosen to use a macOS Passkey.
Also, the keychain framework is available to any app that would like to use it. macOS didn’t “intercept” anything. The 3rd party web browser asked the framework for help to create the Passkey you asked it to create.
Initially the customer is not provided with any choice upon upgrading the OS having new functionality enabled. As previously indicated I have turned off the settings as suggested repeatedly before making my first post, and still the OS does not (always) adhere to the settings "Privacy & Security" which disabled access to the 3rd party browser. This alone is stunning.
Overall, this is typical of rushed out software not yet fully worked out and ready for deployment in Release channels.... Not even insanely adequate
You can't disable in the OS what features the 3rd Party Browser asks to use. This use of a Passkey has absolutely nothing to do with Passwords or passwords. Passkeys are not passwords and can be managed by the Passwords app. When you logged into some website on your 3rd Party Browser, you asked it to create a passkey to access the site. You may have thought you were just creating a password, but that isn't what it created.
The dialog you posted is not the app asking for access. You created a very much macOS entity called a Passkey and the OS asked how you wish to manage that passkey.
And, even if you disable access after the first request by the browser, I would certainly expect the browser to ask you if you want to allow it access for an item you created to securely log into something within the browser. However, that is not what that dialog is asking.