F5Access | MacOS Sonoma

A number of issues were reported in this thread. And we thank you for that. F5 Support worked with each one to find out the root cause and created this article to summarize the list of known issues you may encounter. While waiting for a new release, please refer to K000139761: Overview of F5 Access issues on MAC Sonoma for more information. If the issue you are facing is not listed in the article, for

• VPN users: As every BIG-IP APM access policy is unique and different IT administrators may implement different security requirements for each organization, please contact your IT administrator to report the issue.
• BIG-IP APM administrators: Use the notes in the article which may resolve the issue you are facing at the first instance. Should you require assistance, please do not hesitate to contact F5 Support.

Thank you for your patience as we work towards releasing a new version. There has been a few dates mentioned in this thread, going as far back as March 2024, on the expected release date. If you'd previously received an ETA from F5, we apologize that the date can change due to unexpected issues that necessitate additional development/testing. In the meantime,

• we are committed to providing regular updates here. You can subscribe to updates on this thread by selecting the bell icon at the top right.
• If you encounter issues, it could be one the issues already discovered here:
  https://community.f5.com/discussions/technicalforum/f5access--macos-sonoma/322042/replies/330018. 

Same there; cannot use F5 Access after upgrade to Sonoma 14.4

Hello Letakeda, do you have any news? Thank you

I'm going to update the title of this post Sonora > Sonoma to help others find it - especially so as we work towards a technical solution.

Quick update to reflect for you all that despite the gaps between messages here - there is quite a bit of activity within product, support, and community to get this sorted out.
I have a high-degree of confidence that proper guidance is forthcoming.

Thank you all for your persistence, engagement, and constructive feedback on this issue specifically AND (meta for a second) for illustrating for us some opportunities we have for improvement generally.

It bears repeating that we, in DevCentral and F5 Support, have been working assiduously over the past few quarters to 'robustify' the end-to-end pathways for our F5 community at large. Whether it's deployment support, general guidance, product optimization, peer networking, or initial discovery and exploration - this thread alone serves as a microcosm that will help us all improve - thanks to you.

More soon.

General update:

The last plan of action did not resolve the issue (but ya'll know that already).

The new plan of action is in progress. I expect the owner (@letakeda) of the ticket to get an update sometime relatively soon.
I am adding myself to the watchlist for the ticket and will do my best to update this thread when I get further information - especially when it is actionable.

Thanks again for being integral parts of our DevCentral community.

Lief

Latest I heard about on the case is this:
A review of the logs showed

"the server is requesting a certificate from the client and F5 Access cannot access the private key"

Guidance from there is to

"...ensure that if performing client cert auth, the client certificate is installed and accessible from F5 Access."

This is, I think, just one customers' logs, which then assumes the common thread of "performing client cert auth".

If you can confirm that you are NOT performing client cert auth and you still have an issue 'smash that reply button' and let us know. 

Hope this helps.

Hello, any updates?