Safari plugins support

Would it be possible, as an intermediate step, to allow the iOS app to be used on the Mac? This should be possible at least for Apple Silicon Macs. This would make the whole Passbolt experience practically browser independent. Perhaps even an integration in the Mac password engine could be similar to what exists in your iOS code …

I really can understand why Safari isn’t supportend.
After the death of IE11, Safari took it’s place by being the worst browser to support.
There are so many not or wrong implemented web standards in that thing.
Well under iOS there isn’t an other option for the engine, so I think most iPhone users wouldn’t get the difference, as there browsers are all safari at core.

Lack of Safari support is still a significant issue today for our company.

At the very least, a Mac app that supports Passbolt that would load from a URL (this is what Slack does today) would be wonderful.

1 Like

Would it be feasible to allow the iOS app to be run on Apple Silicon Macs? This should solve at least part of the problem, i.e. removing the reliance on a second browser.

1 Like

@mkerz-dcc we were exploring this, we had a prototype but there are still some issues with password autofill / keyboard, etc. so we didn’t enable it.


Safari is still 20% of the market, and Passbolt seems to prefer support Firefox 6% of the market.

@remy did you mean that there is a Desktop Application in developement for Mac?
If you can relate to this topic it will be great: Desktop Application (Mac/Windows)

@clovs there was an attempt at converting/extending the ios mobile app to desktop (or at least tablet) app but it was not deemed a feasible endeavour. So we’re back to square one.

Historically we favored Firefox yes, as it was the first browser supported by Passbolt. Now we support all browsers that have a “regular” implementation of web extension format (e.g. brave, edge, firefox, chrome, etc.). Safari being apple product it has it’s own quirks and ways of working that differs from other browser for example when it comes to how webextension are loaded or how permissions work. We’ve done a prototype that kind of works but that is not ready for production. As mentionned earlier our goal is first to finish the migration to Manifest V3, then add safari support. Bear with us, we don’t have hundreds of developers on the payroll yet.

1 Like

As @Nugorra, I can also understand why Safari is not supported.

If if you had a real Desktop App federing the all stuff (the vault).
Would it not be easier and more secure to make some browser extension
that just speak to the DesktopApp (the vault)?

Yeah because, all the stuff in a browser extension scare me a little :cold_sweat:

That would be a big shift of architectures. Also there are a lot of companies that don’t want desktop apps, so it would need be one of the webextension mode.

Mailvelope did this a while back (and we even helped), they have an option where the extension would talk to gnupg directly, for people who don’t want the crypto to be in the browser. From what I have heard from Thomas, the project lead there, it’s a support nightmare as these integrations are brittle.


I’m not an Apple user but was reading about the Orion browser. It is reported to work with Chrome and Firefox extensions. Has anyone tried it?

So I was watching the Update to webkit and wwdc2022…

The person was signing into the App demoing “PassKeys” and the username was “garret” Lol. Reminded me of a familiar name :eyes: :laughing:

Just an update. I think Making a Safari plugin might have just gotten easier… i think, due to the introduction of Passkeys.

To checkout the username “garret” it’s at 02:04-02:06



It’s always seemed to be commonly spelled with one T, so this is a surprise to see. Full disclosure: it’s not me, and yes my parents named me after a furniture store.

That’s interesting, I just assumed someone might have taken the username “Garret” and you simply added the extra “t”. Good to know :slight_smile:

That thought never even crossed my mind until now. Completely forgot that there’s a furniture store as well. You shall own that store one day :slight_smile:

Sorry for the off topic sidebar lol



I am moving from Kaspersky and it’s very difficult to find a password manager supporting all browsers/desktops.
As @clovs suggest a desktop application can certainly help suporting more easily all browsers.
It would be a big shift of architectures at first, but a game changer at the end.
And a real european alternative!!


I made a little search about building a Safari app extension, and how adblockers do.
And to do it you have to build an xcode application,
this application will be displayed in your Application Folder with other desktop Apps.

Ok there is no interface, but it’s like a desktop app.
If you open it, it open a desktop window and you can have a link to safari or have some parameters about the safari extension.

From the Apple Developers Documentation

But at the end this is just a Desktop Application, with only the Safari extension part.
Don’t hesitate to upvote this thread => Desktop Application


Given that Edge is now supported, and Safari is still not, @Bob do you have the ability to update the title of this thread to reflect that (by removing Edge from the subject)?

@gene it’s updated, to reflect that edge is done. Cheers,

Hello all,

There is any news about safari compatibility ?


Hello @SHASKAN and welcome to the forum !

There are progress being made on this. It’s still hard to give a clear ETA for it though. For the moment we experiment it and try to fix the different issues we are encountering.

The experiment done is based on the Chrome extension thanks to a tool that converts an existing browser extension to a Safari extension. At the moment, I can do a full recover of an account in a stable way which is already a good progress (before it works when it wanted, now it works thanks to the recent rework of the port management and compatibility improvement for the manifest version 3).

There are other important issues that need a solution like the opening of the Quickaccess which troubles are caused by problems related to Javascript’s Promise management and maybe polyfills (still, not 100% sure yet but, we got similar issues on the Desktop App). Those are used everywhere in the browser extension. Also, another problem is the authentication, as I said the account recovery is ok but it finishes to a sign in process that fails. Passbolt uses GPGAuth mecanism that works here but in the end there’s a cookie delivered by the server and the Passbolt Safari’s extension seems not willing to use it making the server refusing to accept any authenticated request.

Those are the 2 main issues at the moment, there are others like error showing cross-origin access attempt, regular expressions that doesn’t work the same as for the other browsers, some warnings to be checked when converting the extension to a Safari one.



Thanks a lot for the feedback !

Wish you good luck for the dev :).

Have you any estimate of the release date/month/year for Safari extension ?